Possible conflict with Foreman about dotenv

[bkeepers]

Foreman uses dotenv. Can you give more information on your two environments and how they're being loaded?

[obromios]

The two environments are running as a Virtualbox Ubuntu 12.04 guest on a windows machine. Both are running Rails 3.2.12. The .env file is in the root. If I do bundle, then I see the following entries for dotenv

Using dotenv (0.9.0) 
Using dotenv-rails (0.9.0) 

Please let me know if you need any more information about how it is loaded.

One clue might be the .env file that is on the system that is not working looks as follows:

RACK_ENV=development
TEMP_ME="here"

When I load up the system, I can run console and if I type ENV["RACK_ENV], it returns "development" but if I type ENV["TEMP_ME"] it returns nil. If I edit the .env file to change the RACK_ENV variable to something else and then run rails console, the value of RACK_ENV does not change, so it looks like it is being loaded up somewhere else. However, if I search through all my project files, I can not see anywhere obvious that this is happening.

Chris

[obromios]

As well, the contents of my Procfile is:

web: bundle exec rails server thin -p $PORT -e $RACK_ENV

[bkeepers]

Setting RACK_ENV or RAILS_ENV in .env is a chicken-egg problem. By the time .env is loaded in your rails app script/rails console, the environment has already been chosen. It works through foreman because it pre-loads .env before bootstrapping your app.

I would strongly recommend setting RACK_ENV in /etc/environment on your server.

[obromios]

Thank you