ENV vars not loaded from environments or application.rb about dotenv

[willglynn]

Alternately, to load environment variables immediately, we could specify something like:

gem 'dotenv', :require => 'dotenv/load'

This behavior could also be useful outside of a Rails context.

[bkeepers]

Environment variables are currently loaded as part of the initialization process. This could probably be done when the gem is loaded.

[fesplugas]

Maybe would be interesting to explain on the documentation in which parts of the application you cannot use ENV vars when using dotenv. As far as I know:

• config/application.rb
• config/environments/*

[bkeepers]

I just pushed ed610ea, which uses the #before_configuration, which makes it work in config/environments/*. config.application.rb still needs more investigation.

[weppos]

I run into the same issue today, trying to make the ENV['MEMCACHE_SERVERS'] variable available to the cache_store.

config.cache_store = :dalli_store

ed610ea doesn't solve the issue because the config calls are evaluated before before_configuration is executed (reference).

I solved it manually loading it in my application.rb file immediately after Bundler setup.

if defined?(Bundler)
  Bundler.require(*Rails.groups(:assets => %w(development test)))
end

Dotenv.load ".env.#{Rails.env}", '.env'

module MyApp
  class Application < Rails::Application

However, in this case the .env is loaded twice because the before_configuration still exists. It would be great if the library understands where a #load call has already been execute and skip subsequent calls unless forced.

[weppos]

@willglynn If you load it at bundler level, I'm not sure you will be able to access Rails.env