dgaviria/Bookmark-Zone — pull request #1 by stevenjenkins (2011-12-23 03:21:12+00:00)
Title: Demo2

I did some testing, and this branch seems to be the minimal set of changes to get your site working on Heroku. Overall, the asset pipeline in Rails 3.1 seems to be a major source of confusion (I looked at StackOverflow, and there this link, http://stackoverflow.com/questions/7275636/rails-3-1-0-actionviewtemplateerrror-application-css-isnt-precompiled, along with numerous related ones).

However, with these changes, you should be able to get your work done on Heroku:

1- d84b98b3 - a somewhat minor cleanup to only load pg in production, but especially to avoid trying to load sqlite3 in production -- that will break on Heroku
2- 563c87e87 and c345d75 set up so that Heroku will build the assets for you, and any assets not built by the Rake task will be built on demand (and for some reason, default.js would never get built by Heroku as part of the Rake task).

The other key point is to create a Cedar stack application; e.g.,
heroku create --stack cedar
The default stack (Bamboo) is problematic with Rails 3.1.

Thus the steps to set up a 3.1 app on Heroku would be:

1- Create the Rails app locally
2- Make the commits I list above
3- Create a Cedar stack Heroku app
4- git push to heroku
5- heroku run rake db:migrate

and at that point, all should be well. Note that you should be able to merge my pull request and then create a new heroku app from that (because your existing one is probably Bamboo, not Cedar), run db:migrate, and you should be up and running.

Please try that out and let me know how it goes. Also, if you have other issues, let me know.

Thanks,
Steven