You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I find myself quite often dealing with projects that have several .env files, i.e. something like .env for general settings and .env.production/.env.development/.env.build which overwrite settings from .env for certain scenarios.
Currently my way to work with this is to set dotenv-load (to load the .env globally) and then manually add source .env.{{mode}} && ... to every command.
I wonder if we could allow to load multiple dotenv files in order, maybe through having dotenv-filename being a list of items or a colon-separated string?
this would require the files to all be in the same directory, so maybe we simply have a list of paths (["./packages/ui/.env", "./packages/backend/.env"]?
The text was updated successfully, but these errors were encountered:
I find myself quite often dealing with projects that have several .env files, i.e. something like
.env
for general settings and.env.production
/.env.development
/.env.build
which overwrite settings from.env
for certain scenarios.Currently my way to work with this is to
set dotenv-load
(to load the.env
globally) and then manually addsource .env.{{mode}} && ...
to every command.I wonder if we could allow to load multiple dotenv files in order, maybe through having
dotenv-filename
being a list of items or a colon-separated string?Something like this maybe:
this would require the files to all be in the same directory, so maybe we simply have a list of paths (
["./packages/ui/.env", "./packages/backend/.env"]
?The text was updated successfully, but these errors were encountered: