[Master Class] [Designer and Developer Workflow] [Generating the Scaffold]

So, up to this point, we've generated a new Rails project.

We haven't really done anything with it, but we've created the skeleton for it,

and we've set up our GitHub account and sent the details over to Nick.

So hopefully by now, he can at least pull the project and set up the basic Rails stuff.

And our next step is to go ahead and configure it and see if we can get it up and running.

Now, I just got a message from Nick.

Let's go ahead and take a look.

"Hey Jim, I was wireframing the show view for the jobs...and I was thinking

that there were a few fields that we could add."

"I know we originally agreed on just having a job title and description for the job."

"But I think it would also be nice to add the name of the company

and a details link in case the company wants to include an external link

so they can see more details about the job."

Okay, so it looks like we've gone from having our job just be a title and description

to now having a company name and a details link.

That looks like a pretty easy change, but I'm glad Nick went ahead and sent that

as soon as he did so I don't have to change an existing model

because I was just about to do that, so the timing is perfect.

So, let's add that.

All right, so let me just go ahead and reply to him.

"Hey Nick, that all sounds pretty good."

"I'll go ahead and add those, and I'll let you know exactly what the different fields are

when I go ahead and generate it."

"Give me a few minutes and I'll go ahead and push the scaffold up with these details."

So now, let's go ahead and do what we promised to do.

Before we can scaffold anything, let's go ahead and see if our Rails application is even running.

So, the first thing I want to do is run bundle install.

So now, we've run bundle and it's gone ahead and installed all the dependencies

that are needed to run this application.

Let's start up our server and see if it works.

So, we'll type in "rails server" or just "rails s," and let's go over to our browser.

And if we load up local host 3000, we can see the Rails welcome screen.

So, it looks like our server is up and running.

Let's go ahead and generate our first scaffold.

So, let's go ahead and stop the server, and we will be generating a new scaffold.

If you want to learn more about scaffolds, go ahead and watch our videos on Ruby on Rails,

so I'm just going to be going through this pretty quickly.

We'll do "rails g" for Rails generate, and we're going to create a scaffold.

And our model is going to be called a job.

And if we look at our information, we need a title, description,

company name and details link.

Our title is going to be "string," our description is going to be "text,"

our company name will be "string," and the details link will be another string.

A pretty simple model.

So, let's see what happens when we install ithis.

All right, that looks pretty good.

However, I did notice something.

We did generate html.erb files.

Now, Nick and I decided we wanted to work on HAML and SASS,

so let's go ahead and destroy all this, install HAML and SASS,

and see if we can get the correct generators to work.

So, we'll type in "rails destroy scaffold job."

And that's gone and undone everything that the generator did.

So, let's go ahead and install HAML.

So, let's open up our gem file.

And we're going to go ahead and add the gem HAML as a dependency.

So, we'll add "gem haml" and we'll save that out.

So, let's go back to our terminal and type in "bundle install"

so we can install HAML.

So now, we've installed so our Rails application will now be able to handle .haml files.

Let's go ahead and run our generator again and see what happens.

Now, we're still getting our index.html.erb, and that's because installing HAML

only allows us to read HAML files, it doesn't install any generators

for our scaffold to generate in HAML.

Now, we could go in and rename the ERB file to HAML and recreate them all ourselves,

but it'd be nice if our scaffold did come with HAML by default.

Now, one tool we can do to have Rails generate HAML is use the gem called "HAML Rails."

And this will add the generators that will create our different scaffold views

in HAML instead of .erb files.

So, we'll go back, add HAML Rails to our gem file,

save it out, and run bundle install again.

So now, we have HAML Rails installed.

Let's go ahead and destroy our original scaffold again,

and then let's go ahead and rerun our scaffold generator and see what we get.

It looks like it generated the HAML views, which looks pretty good.

So, if we go into our text editor, let's take a look.

So, we have our jobs, looks like our index.html.haml.

Looks like HAML to me and that'll be a good starting point for Nick to work off of.

And so, I think we're good to go ahead and stick with this generator.

So, let's go ahead and set up our database.

Now, by default, we're using SQLite3, so we'll run the task

"rake db: create" to go ahead and create our database.

Done, and our generator set up a migration for us for our jobs,

so we'll run "rake db: migrate."

And it's gone ahead and created the table "jobs."

So, if we start up our server, we can see where we're at.

So, going back here to local host 3000, the root page is still going to be the welcoming page.

And let's go to /jobs.

All right, we got our normal listing here.

We can create a new job, say "Ice Cream Taster."

Add some text and we'll give it a company name, and we'll give it a details link.

Save it out.

We have our show page for jobs, and we have our listing here.

And this is enough to send over to Nick where he'll begin working on the layout,

the user interface, the user experience and all of that

to actually make the app run properly.

So, I think this is a good point for a commit, so let's go ahead and do just that.

We'll stop the server.

We'll do "git add ."

We'll do "git commit," and we'll say we "Generated the jobs model."

And I'm going to go ahead and "push origin master."

And now it is up on GitHub.

So now, I'm going to go ahead and send a message to Nick telling him about this,

and letting him know he can start working on the views.

"Hey Nick, I went ahead and ran the generator for our jobs, so if you pull now

you'll have the jobs scaffold at /jobs."

"I named the fields: title, description, company name and details_link,

and of course you have the created_at and updated_at fields for the dates."