Mod_rails is defaulting to development mode

Rails
1

I just installed mod_rails on a brand new Hardy server and for some
reason it is defaulting to development mode. I even put RailsEnv in
the apache config file.

Any ideas on what might be causing this?

2

Okay I disabled mod_rails and noticed that the app is still defaulting
to development mode (i did a rake db:create with no password on the
development database to throw up and an error if it uses the
development database) … so I guess it’s some rails thing or ruby
thing that is going crazy … any ideas?

3

Did you try setting it in the config/environment.rb?

best.
mike

4

Yea i can set it there but it only changes it for the web… when I do
db:migration, it tries to use the development database

5

Okay thanks to help from Slicehost.com people, here is the code that i
added to my .bashrc file:

export RAILS_ENV=production

6

Right, it has nothing to do with mod_rails since you are doing rake. By
default rake assumes development so you don’t end up shooting yourself
in the foot.

To run with production use:

rake db:create RAILS_ENV=production

Hth,
Long

mel ram [email protected] wrote:
Okay I disabled mod_rails and noticed that the app is still defaulting
to development mode (i did a rake db:create with no password on the
development database to throw up and an error if it uses the
development database) … so I guess it’s some rails thing or ruby
thing that is going crazy … any ideas?