You may be learning Rails & you read that you have to create a “scaffold” to get your Rails application started…
You can do this using the
rails g scaffold command.
But what is scaffolding?
“Scaffolding is a temporary structure used to support a work crew to aid in the construction, maintenance and repair of buildings, bridges and all other man-made structures.” – Wikipedia
Translated into Rails:
A scaffold is a set of automatically generated files which forms the basic structure of a Rails project.
These files include:
A new route.
And a migration to prepare your database.
Let’s see an example!
An example of scaffolding a project for a website about books would look like this.
rails g scaffold books
You should see a lot of text scrolling by, which details the files being created.
This example creates:
resources :booksroute added to your
app/views/books(five in total)
That’s a lot of stuff.
If you want to undo this scaffolding, right after creating it, you can use the following command.
rails d scaffold books
Where “d” means “destroy”.
Keep in mind that this will DELETE the files created by the scaffolding process.
Before you can use your scaffolded code you have to run your migrations to update your database schema.
rails db:migrate command.
If no error messages show up, you’re ready! You have a basic structure for your new Rails application, or for a new feature that needs a new model, views & corresponding controller.
Open your browser to
localhost:3000/books & you should be able to see the results!
Your model only gets timestamp fields, which means that the only information that you can record about your books (or whatever model you’re working with) is the time at which they were created, or updated.
Here’s how to scaffold with extra fields:
rails g scaffold books title:string author:string publication_year:integer
If you generate your scaffolding like this, you’ll have 3 fields to work with.
A title, an author, and a publication year.
That’s a bit more interesting than just having the database timestamps.
This the same syntax we use for creating migrations with
rails g migration.
Scaffolding creates things you may not need or want right now.
But Rails is nice.
You can create individual components, like controllers, using the
rails g (g for generate) command.
This ensures that the files are created using the correct naming conventions. It can also save you the work of having to manually create these files.
It’s considered good practice to delete auto-generated files that you don’t plan on using.
You’ve learned about scaffolding in Ruby so you can quickly jumpstart a new Rails application to practice with.
As you learn more you may want to let go of scaffolding.
But you can still generate individual controllers, models, or view files when you need them.
Thanks for reading! 🙂