Si Forster said the following on 04/27/2010 11:06 AM:
> Okay so a bit further along now.
>
> Currently I need to specifiy "RAILS_ENV=production" in the command line
> after and db based changes such as "rake radiant:extensions:xxx:update" or
> "db:migrate".
>
> Any idea why this might be the case?
You're using Passenger, right?
Passenger seems ignore the ENV and RAILS_ENV and always run as
production. I believe this is documented and I recall it being
mentioned here when I encountered that last year :-)
Of course access though Passenger is only for web-based access.
For command line you have to specify it explicitly, as you point out.
> I've got ENV['RAILS_ENV'] =
> 'production' specificed in my environments file but this doesn't seem to
> make a difference.
I observed this too and I don't know why it is.
Maybe its in the libraries they use ...
Try compiling your own version of RAKE.
> Hopefully my findings will help others using dreamhost.
BTDT.
--
The maxim that people should not have a right till they are ready to
exercise it properly, is worthy of the fool in the old story who
resolved not to go into the water till he had learned to swim.
--Macaulay
_______________________________________________
Radiant mailing list
Post: [email protected]
Search: http://radiantcms.org/mailing-list/search/
List Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Radiant: http://radiantcms.org
Extensions: http://ext.radiantcms.org
