Permalink
Browse files

Add bundler and asset compilation to step 11.

Added the necessary steps to keep bundler happy on heroku for Rails 3.1
as well as a brief description of the purpose of the Gemfile and
bundler.
  • Loading branch information...
1 parent 640a76f commit 34f28a2d238526849ad391b0d90e425cf2981e8f @nuclearsandwich nuclearsandwich committed Dec 3, 2011
Showing with 17 additions and 2 deletions.
  1. +17 −2 lessons/11.yaml
View
@@ -24,8 +24,10 @@ steps: |
end
In your terminal, try: (**note:** there is a period after the word
- add in the first line)
+ add in the third line)
+ $ bundle install --without production
+ $ rake assets:precompile
$ git add .
$ git commit -m "Added topics"
$ git push heroku master
@@ -38,6 +40,19 @@ explanation: |
while we're developing on our computer (the development group) but when
deploying to heroku (the production group) we want to use the `pg` library,
which is made for the type of database that Heroku uses.
- * We've done the first three steps before, so we won't go over that again...
+
+ * Bundler is how Ruby projects keep track of the gems that they use. We told
+ bundler what we wanted to use in the `Gemfile`, now we need make sure those
+ gems are installed. Since we don't have the type of database heroku does, we
+ skip the production gems. Don't worry though! Bundler still logs them so
+ Heroku will install them when they get your code.
+
+ * Newer versions of Rails do more to help you manage any Javascript or CSS in
+ your application. Since Rails has CSS generated by the scaffold, we have to
+ make sure it's ready to be deployed to Heroku. That's what the `rake
+ assets:precompile` is for.
+
+ * We've done the next three steps before, so we won't go over that again...
+
* `heroku rake` executes a rake task on your server, in this case,
`db:migrate`, just like you did locally.

0 comments on commit 34f28a2

Please sign in to comment.