I had been known to Heroku for Ruby on Rails hosting and to date I believe I'm really likely to enjoy it. Just wondering basically anybody available might help me evaluate which is wrong.
I follow there instructions for creating an application on the website site, create and commit git, push the code also it turns up at http://mylifebattlecry.heroku.com (though the majority of things i did is incorporated in the /posts/ path) After I visit enter a brand new "publish" (since this is type of your blog platform) I recieve the 500.html error and basically everything shuts lower. Can't even return to the page which i joined the publish.
Appears in my experience something is wrong using the database setup. Used to do because they recommended including ...$ heroku rake db:migrate, and absolutely nothing.
Just wondering if anybody knows off hands things i am doing wrong. Listed here are the instructions they provide for reference:
Install the Heroku jewel:sudo jewel install herokuCreate a brand new git repository for the application (should you haven't already):
compact disc myapp git init &lifier&lifier git add . &lifier&lifier git commit -m "first commit"
Produce a new Heroku application:
heroku create Produced http://sharp-fall-42.com/ firstname.lastname@example.org:sharp-fall-42.git Git remote heroku added
NOTE: The app's title is produced instantly don't be concerned, you are able to relabel it anytime.
Deploy your code:
git push heroku master
Run migrations (or any other bootstrap tasks):
heroku rake db:migrate
Open the used application inside your browser: heroku open
This is actually the ..$ heroku logs whether it helps:
brandon-gadocis-mac laptop-professional:mylifebattlecry bgadoci$ heroku logs -application mylifebattlecry ==> dyno-629271.log <== ==> production.log <== # Logfile produced on Sun November 22 18:26:06 -0800 2009 Processing PostsController#index (for 126.96.36.199 at 2009-11-22 18:26:07) [GET] Rendering template within designs/posts Rendering posts/index ActionView::TemplateError (PGError: ERROR: column votes.publish_id doesn't exist LINE 1: Choose count(*) AS count_all FROM "votes" WHERE ("votes".pos... ^ : Choose count(*) AS count_all FROM "votes" WHERE ("votes".publish_id = 1) ) online #58 of application/sights/posts/index.html.erb: 55: </div> 56: <div id="election"><br/> 57: <div id="votes"> 58: <%= pluralize publish.votes.count, 'Person' %> such as the above BattleCry. <br/> 59: </div> 60: <%= link_to "Comments (#publish.comments.count)", publish %> 61: </div> application/sights/posts/index.html.erb:58 application/sights/posts/index.html.erb:51 application/sights/posts/index.html.erb:45:in `each' application/sights/posts/index.html.erb:45 application/remotes/posts_controller.rb:11:in `index' /home/heroku_rack/lib/static_assets.rb:9:in `call' /home/heroku_rack/lib/last_access.rb:25:in `call' /home/heroku_rack/lib/date_header.rb:14:in `call' thin (1..1) lib/thin/connection.rb:80:in `pre_process' thin (1..1) lib/thin/connection.rb:78:in `catch' thin (1..1) lib/thin/connection.rb:78:in `pre_process' thin (1..1) lib/thin/connection.rb:57:in `process' thin (1..1) lib/thin/connection.rb:42:in `receive_data' eventmachine (.12.6) lib/eventmachine.rb:240:in `run_machine' eventmachine (.12.6) lib/eventmachine.rb:240:in `run' thin (1..1) lib/thin/backends/base.rb:57:in `start' thin (1..1) lib/thin/server.rb:150:in `start' thin (1..1) lib/thin/remotes/controller.rb:80:in `start' thin (1..1) lib/thin/runner.rb:173:in `send' thin (1..1) lib/thin/runner.rb:173:in `run_command' thin (1..1) lib/thin/runner.rb:139:in `run!' thin (1..1) bin/thin:6 /usr/local/bin/thin:20:in `load' /usr/local/bin/thin:20 Rendering /disk1/home/slugs/88382_601a216_9803/mnt/public/500.html (500 Internal Server Error)
Are you certain you've migrations for your tables.
You could do this heroku rake db:schema:load to simply load a brand new schema
The key line within the logs is:
PGError: ERROR: column votes.publish_id doesn't exist
What this means is the database on Heroku does not possess the schema your application is attempting to make use of.
Make certain you've got a migration that produces the tables how you want, commit the alterations, then run:
heroku rake db:migrate and you will be all done.
To check, begin with a clean local database (if using sqlite, just nuke db/development.sqlite3), and run
rake db:migrate in your area. Whether it creates the local machine, it will then focus on Heroku.