Ruby On Rails Lesson
Seen from the outside, this chapter hardly accomplished anything: We started with static pages, and ended with . . . mostly static pages. But appearances are deceiving: By developing in terms of Rails controllers, actions, and views, we are now in a position to add arbitrary amounts of dynamic content to our site. Seeing exactly how this plays out is the task for the rest of this tutorial.
Before moving on, let’s take a minute to commit our changes and merge them into the master branch. Back in Section 3.1.2 we created a Git branch for the development of static pages. If you haven’t been making commits as we’ve been moving along, first make a commit indicating that we’ve reached a stopping point:
Then merge the changes back into the master branch using the same technique as in Section 1.3.5:
Once you reach a stopping point like this, it’s usually a good idea to push your code up to a remote repository (which, if you followed the steps in Section 1.3.4, will
If you like, at this point you can even deploy the updated application to Heroku: