Change remaining rake commands to rails

Mostly `rake db:migrate` and `rake routes`.

Fixes #590

Author: tjgrathwell

sites/en/installfest/deploy_a_rails_app.step

@@ -153,7 +153,7 @@ step "Deploy your app to Heroku" do
 
     message "This process will probably take about twice as long as your 'bundle install' and then will return you to your console prompt.  If it takes longer than that, talk to a TA."
 
-    console "heroku run rake db:migrate"
+    console "heroku run rails db:migrate"
 
     result <<-OUTPUT
       Migrating to CreateDrinks (20160706063236)

sites/en/intro-to-rails/_deploying_to_heroku_again.step

@@ -17,9 +17,9 @@ step "Push changes to Heroku" do
 end
 
 step "Run database migrations on Heroku" do
-  console "heroku run rake db:migrate"
+  console "heroku run rails db:migrate"
   message "This tells Heroku to run your migrations on its database, like
-running `rake db:migrate` locally."
+running `rails db:migrate` locally."
   message "Heroku's database is separate from the one on your computer, which
 means it needs to be updated every time you make changes to the structure of
 your database."

sites/en/intro-to-rails/allow_people_to_vote.step

@@ -38,7 +38,7 @@ steps {
     RUBY
 
     message <<-MARKDOWN
-      Verify that upvote route was added successfully by checking the output of `rake routes` or [http://localhost:3000/rails/info](http://localhost:3000/rails/info). You should see a line that looks like this:
+      Verify that upvote route was added successfully by checking the output of `rails routes` or [http://localhost:3000/rails/info](http://localhost:3000/rails/info). You should see a line that looks like this:
 
       ```
             Prefix Verb   URI Pattern                  Controller#Action

sites/en/intro-to-rails/creating_a_migration.step

@@ -25,22 +25,19 @@ steps {
   }
 
   step {
-    console "rake db:migrate"
+    console "rails db:migrate"
     message "This tells Rails to update the database to include a table for our new model."
   }
 }
 
 explanation {
 
-  h2 "Rake"
   message <<-MARKDOWN
-`rake` (**r**uby m**ake**) is a tool that allows you to run small Ruby programs (**tasks**) that you use often in your application.
-
-Here, `rake db:migrate` is a task provided by the Rails framework. It uses the migration file we just created (`db/migrate/201xxxxxxxxxxx_create_topics.rb`) to change the database. Database migration files can be crucial to code collaboration.
+Here, `rails db:migrate` is a command provided by the Rails framework. It uses the migration file we just created (`db/migrate/201xxxxxxxxxxx_create_topics.rb`) to change the database. Database migration files can be crucial to code collaboration.
 
   MARKDOWN
 
-  tip "You can run `rake -T` to see a list of all the `rake` commands your app currently responds to, along with a short description of each task."
+  tip "You can run `rails --help` to see a list of all the `rails` commands your app currently responds to, along with a short description of each one."
 }
 
 

sites/en/intro-to-rails/setting_the_default_page.step

@@ -48,11 +48,11 @@ explanation {
     possible URLs. To explore the URLs in more detail we can use the
     terminal.
 
-  At the terminal type `rake routes`. You should get something that
+  At the terminal type `rails routes`. You should get something that
   looks like this:
 
   ````
-    $ rake routes
+    $ rails routes
 
         Prefix Verb   URI Pattern                Controller#Action
         topics GET    /topics(.:format)          topics#index

sites/en/intro-to-rails/voting_on_topics.step

@@ -10,7 +10,7 @@ goals {
 steps {
   console <<-SHELL
 rails generate model vote topic_id:integer
-rake db:migrate
+rails db:migrate
   SHELL
 }
 

sites/en/job-board/store_jobs_in_the_database.step

@@ -61,10 +61,10 @@ RUBY
 
 message "Now we need to execute this file, so that the database schema gets updated."
 
-console "rake db:migrate"
+console "rails db:migrate"
 
 message <<-MARKDOWN
-  This uses a utility called rake to run a task called `db:migrate`, which in turn looks through all of your migration files and runs any that haven't already been run at some point in the past.
+  This tells Rails to run any migration files that haven't already been run at some point in the past.
 MARKDOWN
 
 discussion_box "Why do we use migrations?",

sites/en/message-board/commands.md

@@ -32,7 +32,7 @@ Create a new [Rails model]
 
 Update the database to match what you have described in your code
 
-    rake db:migrate
+    rails db:migrate
 
 Run the application locally (Ctrl-C to quit)
 
@@ -44,7 +44,7 @@ Start an interactive Ruby session that knows about your Rails models (type 'exit
 
 Print the routes for your application
 
-    rake routes
+    rails routes
 
 ## Browser
 

sites/en/message-board/install_devise.step

@@ -16,7 +16,7 @@ discussion do
 message <<-MARKDOWN
 * What is Devise?
 * What files did Devise add to your rails app?
-* Someone Who Knows: explain how to read the output of the command `rake routes`. What does it give you? How is it helpful?
+* Someone Who Knows: explain how to read the output of the command `rails routes`. What does it give you? How is it helpful?
 * How will you add the log out link? What's the syntax for a DELETE action?
 * You're going to be editing your application layout to add error messaging. If you haven't already, discuss the relationship between the application layout and all the other views you'll be creating. 
 MARKDOWN
@@ -36,7 +36,7 @@ message <<-MARKDOWN
 * The convention for naming models is to capitalize the first letter, like: User. 
 * When you run `rails generate devise:install`, you get five instructions for things to configure. 3 & 4 are good to do.
 * The routes file goes through many common types of routes in the comments. This is also your friend.
-* Devise has some magic that will help you with your logout link. Run `rake routes` and look for a route that helps you sign out. 
+* Devise has some magic that will help you with your logout link. Run `rails routes` and look for a route that helps you sign out. 
 * You'll probably want to show the current user's email address only if they are presently signed in, right? Devise has a helper for you.
 * Optional: any time you generate a model in rails, you can use Rails Console to look at that model's methods and behavior interactively.
 MARKDOWN