Support multiple .env files?

[laggingreflex]

Thoughts on supporting multiple .env files?

[toddbluhm]

Yeah I certainly would be open to that. Maybe have it support merging too in the style of Object.assign? Thoughts?

[toddbluhm]

I think if we go this route we will need to do some sort of flag style then so we know exactly when the user has stopped adding env files and we can retain the default behavior (no flags) that is very simplistic and I like that. So maybe something like this for multiple files: env-cmd -e file1.env file2.env file3.env -c node index.js maybe?

Then for the merging aspect, the file to the right will always override the file to the left, meaning that the files will be applied to process.env in order from left -> right.

[laggingreflex]

I've changed my mind on this. Most tools I've come across expect (even advocate) single env file. Docker by default not only recognizes a single .env, it also requires less configuration, whereas its support for having any other file name, let alone multiple of them, is limited.

For this reason I've chosen to go with single .env file, and if need be combine several beforehand.

Also I realized I could just chain env-cmd command to load multiple files:

env-cmd .env-dev env-cmd .env-test npm run tests 

Thanks for taking interest in this. Really appreciate it.