Pretty new to rails/heroku. I created a clean project to help figure out what in the world is happening with heroku. Then I add to it with a:
rails generate controller Pages home contact
http://localhost:3000/pages/home shows exactly what we expect. Commit, push to git, push to heroku. Open the page on heroku and it returns the error page: "We're sorry, but something went wrong."
heroku logs don't seem to have anything interesting, and exceptional isn't registering that anything bad is happenin at all.
UPDATE: I've reduced the logs to an example of the offending bits.
2011-10-06T01:06:05+00:00 app[web.1]: Started GET "/pages/home" for 97.87.14.192 at 2011-10-05 18:06
:05 -0700
2011-10-06T01:06:05+00:00 app[web.1]:
2011-10-06T01:06:05+00:00 app[web.1]: ActiveRecord::ConnectionNotEstablished (ActiveRecord::Connecti
onNotEstablished):
2011-10-06T01:06:05+00:00 app[web.1]:
2011-10-06T01:06:05+00:00 app[web.1]:
2011-10-06T01:06:05+00:00 app[web.1]:
2011-10-06T01:06:05+00:00 app[web.1]: cache: [GET /pages/home] miss
Here's the gemfile I'm running
# gemfile
source 'http://rubygems.org'
gem 'rails', '3.1.0'
group :test do
gem 'sqlite3-ruby', :require => 'sqlite3'
gem 'rspec-rails', '2.6.1'
gem 'webrat', '0.7.1'
end
group :development, do
gem 'sqlite3-ruby', :require => 'sqlite3'
gem 'rspec-rails', '2.6.1'
end
This is just a generic heroku error so you don't display sensitive info to end users. Just type heroku logs
in rails root and you should see the latest server details including your error.
If you have to run migrations the command is:
heroku run rake db:migrate
(Thanks to lampshady)
Migrate your database on heroku then redeploy the app and restart the heroku server. Thats all you need to do.
heroku rake db:migrate
git push heroku master
heroku restart
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With