HostingRails.com

Hi Remco,

Could you please check the environment.rb file. You need to uncomment the following line to confirm you're in production mode:

ENV['RAILS_ENV'] ||= 'production'


Also please check the database.yml file and make sure that you have given the correct enties as mentioned below:

production:
 adapter: mysql
 database: [your_hostingrails_username]_[your_database_name]
 username: [your_hostingrails_username]_[your_database_username]
 password: your_password

For further reference: http://www.hostingrails.com/forums/wiki_thread/1

Also - 99% of these kind of troubles can be fixed with the info in the following two threads:

http://www.hostingrails.com/forums/wiki_thread/15
http://www.hostingrails.com/forums/wiki_thread/9

or if you're having trouble with a Capistrano deployment, a common problem/fix is found here:

http://www.hostingrails.com/forums/deployment_troubleshooting_thread/171

Cheers,

~William

Thanks for that, William. I've now got past that using your suggestion (don't remember seeing it in the instructions... I'll check).

Now my Rails app is "failing to start".

My app is on Rails version 1.1.6 according to environment.rb. The server is on version 1.2.2 according to "# rails -v".

I suppose this is where "freezing gems" comes in.

Would it make more sense to upgrade the app now to 1.2.2 and then freeze it? If so, how?