Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support cascading/multiple env files option #113

Closed
np-kyokyo opened this issue Jul 5, 2024 · 0 comments · Fixed by #115
Closed

Support cascading/multiple env files option #113

np-kyokyo opened this issue Jul 5, 2024 · 0 comments · Fixed by #115

Comments

@np-kyokyo
Copy link

I want such option that npm dotenv-cli package have like below

Borrow from npm dotenv-cli package documentation:

Cascading env variables

Some applications load from .env, .env.development, .env.local, and .env.development.local (see #37 for more information). dotenv-cli supports this using the -c flag for just .env and .env.local and -c development for the ones above. The -c flag can be used together with the -e flag. The following example will cascade env files located one folder up in the directory tree (../.env followed by ../.env.local):

dotenv -e ../.env -c

multiple env variables

Multiple .env files can be specified, and will be processed in order:

$ dotenv -e .env3 -e .env4 -- <command with arguments>
@np-kyokyo np-kyokyo changed the title Support cascading or multiple env files option Support cascading and multiple env files option Jul 5, 2024
@np-kyokyo np-kyokyo changed the title Support cascading and multiple env files option Support cascading/multiple env files option Jul 5, 2024
@venthur venthur closed this as completed in ff86204 Aug 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant