best practices for test environment? about dotenv

[bkeepers]

You can, or you can put something like this after Bundler.require in config/application.rb:

Dotenv.overload ".env.#{Rails.env}"  # or "config/environments/#{Rails.env}.env}"

[rwz]

I don't know if that's the right place to complain but me and lots of other developers I've introduced to dotenv use it for development AND test environments.

I guess that the biggest issue that led to dotenv-deployment was people adding dotenv to gemfile without test/dev grouping and then getting weird behavior in production and spending a lot of time debugging it.

I think dotenv should work in development AND test by default and do nothing in production. It's frustrating to add a separate gem of write glue-code to get the same behavior in test you already have in development. I also can't imagine a situation where you do need dotenv in development, and not in test by default.

[jjb]

I agree with @rwz

[jjb]

@bkeepers any thoughts on what @rwz wrote?

[bkeepers]

You could easily add this in your spec_helper.rb or test_helper.rb:

Dotenv.load(".env.test")