Having a lot of trouble with rails3.1 heroku deploy?

Before your commit run the following to precompile your assets: $> bundle exec rake assets:precompile You shouldn't need to set up anything for the heroku database other than putting gem 'pg in the production section of your gemfile. It figures it all out all the rest on its own Some nice tricks I use quite a bit are: $> heroku db:push $> heroku db:pull Read about push & pull here I develop locally on mysql since it has the best front end IMHO, but you would be fine using sqlite3 or postgres too, depending on how much you want to be working in raw tables.

Before your commit run the following to precompile your assets: $> bundle exec rake assets:precompile You shouldn't need to set up anything for the heroku database other than putting gem 'pg' in the production section of your gemfile. It figures it all out all the rest on its own. Some nice tricks I use quite a bit are: $> heroku db:push $> heroku db:pull Read about push & pull here I develop locally on mysql since it has the best front end IMHO, but you would be fine using sqlite3 or postgres too, depending on how much you want to be working in raw tables.

Hah! , I think it worked. Just tried it with a fresh plain rails app and the rails logo is showing now.

Now I am going to try it with my actual app. Thanks – Spencer Cooley Oct 18 at 4:46 nope not working with my actual app though. Just keep getting the 500 error page – Spencer Cooley Oct 18 at 4:58 If you're having trouble with the pg gem on your dev machine, read here – trogdor33 Oct 18 at 22:55 You'll also want to get your heroku log file using the 'heroku log' command, that should tell you why you're getting the 500 error.

– trogdor33 Oct 18 at 22:56.

I had that problem, but I changed to the cedar stack and that seemed to solve the asset problem. As for the DB, just specify group :production do gem 'pg' end in the gemfile.

– Spencer Cooley Oct 18 at 4:20 I specify it using gem 'sqlite3', '1.3.4', :group => :development – Last Rose Studios Oct 18 at 4:31.

Actually I used the information from both of your answers to get it to work. My asset problem was solved with the bundle exec rake assets:precompile and my db problem was solved by group :production do gem 'pg' end and also adding this: group :development do gem 'sqlite3' end.

1 Heroku will precompile your assets as part of the deployment process - my deployment process of Rails 3.1 applications is a simple git push heroku command. Devcenter.heroku. Com/articles/rails31_heroku_cedar – John Beynon Oct 18 at 7:41.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.