It would be nice to have a .env file, instead of setting the variables globally.
@Sjoerrdd could you elaborate a bit more what you would like to see implemented? I guess you would like to have some wrapper around System.get_env/1 which also looks for .env files so you could use that in your say, dev.exs instead of System.get_env/1, would that be correct?
As for environment variables and setting them for your project, did you already have a look at tools like direnv or autoenv which do some environment variable switching for you?
Personally I currently find myself managing configuration through either explicit values in the dev.exs and test.exs, or through System.get_env/1 in production where I have settings fed through init scripts or docker.
Exactly @rmoorman! 馃檭
Thanks for the quick response,
At the moment I use the standard config files, but my preference is for a .env file as in Adonis & Laravel.
@Sjoerrdd use system level .env file parser like direnv instead.
@Sjoerrdd yet another option to utilize .env files would be a Procfile based tool like foreman or honcho.
The issues tracker is not for feature requests, per the issue template. Thanks!
Most helpful comment
@Sjoerrdd use system level
.envfile parser likedirenvinstead.