When I installed Tracks at A Small Orange, I set database.yml’s Development and Production info to the same database/user, etc.  While everything’s been working fine, I recently realized that the single biggest consumer of my limited disk space is development.log, which grows consistently.  I assume this means tracks is running in development mode. 

Is there a safe way to move things over to production? 

Thanks.

It depends on how you are running Tracks. If you’re running via lighttpd, you can set:


“bin-environment” => ( “RAILS_ENV” => “production” )


inside your fastcgi.server lines in lighttpd.conf.

You can also set the RAILS_ENV variable in Apache somehow, but I’m not sure how you do it on a shared host. It’s probably easier to uncomment the line (line 5) in config/environment.rb:


ENV[‘RAILS_ENV’] = ‘production’


If you’re running lighttpd, restart it.

FYI, running a rails app on a shared server in development mode is a Bad Idea. Development mode rails has increased memory usage and possibly even memory leaks. I learned this the hard way (a warning from my ISP), so I figure I’d warn any readers of this thread…