I added a "w.env" option that takes a hash:
w.env = { 'RAILS_ENV' => production }
You should have it if you're running 0.7.8 or higher.
On Sep 25, 2:03 am, muni <[email protected]> wrote:
> Thanks for your reply,
> for some reason inside the xxx.god file when I refer to ENV
> ["RAILS_ENV"] it is not set and it is NIL.
> I tried it with:
> export RAILS_ENV="production"
> and
> RAILS_ENV=production god -c config/xxx.god
> any ideas?
>
> On Sep 22, 11:08 pm, pete <[email protected]> wrote:
>
>
>
> > Yes, that should work for changing the env for a single command. If
> > you want something a little more permanent (until you end the
> > session), you can do something like this:
>
> > $ export RAILS_ENV="production"
> > $ god -c config/xxx.god
>
> > pete
>
> > On Sep 22, 2:49 am, muni <[email protected]> wrote:
>
> > > Hi,
>
> > > I was wondering if it is possible to set the rails environment from
> > > the command prompt? like RAILS_ENV=production god -c config/xxx.god or
> > > any other way?
>
> > > Cheers
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"god.rb" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/god-rb?hl=en
-~----------~----~----~----~------~----~------~--~---
