Hi Scott,
I have some sites on rails on dreamhost. also my clients sites are
hosted there.
I am not sure of your expertise level in Rails
but some suggestions that I believe can help.
a)change environment.rb to have environment as production
b) change shebang lines on public/dispatch.fcgi to
#!/usr/bin/env ruby
c) make dispatch.fcgi as executable
d) remove your index.html file(it does not run rails, it is served by
your webserver)
e) Have a default route for application home
now try running your app, and check on your shell console if there is a
instance of ruby or dispatch.fcgi
you can do that with
ps axww -o ‘pid command’
if you dont find any there may be other issues
you can go into debugging mode
try to manually run the dispatch.fcgi by running on console “ruby
dispatch.fcgi”
see if there are are any errors or warnings, these errors are not
generally not shown on production environement to browser, all you see
is 500 Application Error
troubleshooting
500 Application Error
Check file permissions for dispatch.fcgi, dispatch.rb
Ruby path used in dispatch.fcgi
Testing db connectivity(script/console)
Db migrations(please do it manually until you are comfortable)
Troubleshooting
File listing instead of running application
Check web server config if domain/subdomain has been mapped to â??publicâ?
folder of the application,
Check .htaccess file is present
Troubleshooting
Application freeze
Try Killing/restarting FCGI processes
Check if rails gem version mismatch, can happen if server rails version
has changed, solution is freezing rails version and unpacking plugins
.htaccess
Web server restart
some of the above info came from my presentation slides , which I used
for giving a talk on “Rails Deployment” in Chennai.rb meet on 8th july
2006
Contact me for rails help, consultancy and hosting
Senthil N.
+91 98406 31021
senthil @ senthilnayagam.com
http://senthilnayagam.com