-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
Multiple --env-file? #7847
Comments
This would be a very useful feature, because if you have multiple docker-compose files you might want to have some development only env variables to extend/overwrite the env variables for the base E.g. I expose some ports in the @leppaott |
That being said, for an homogeneous UX it would indeed make sense to support --env-file as a multi-value flag. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed because it had not recent activity during the stale period. |
so is there any progress on this? It would make sense to support multiple .env files. without attaching them to every single service manually. |
@averon420 this is partially supported thanks to compose-spec/compose-go#348 |
Sounds awesome, thanks! Sadly, I have no idea what I have to do, to get it to working. Can you give me any hint? |
You can't yet. We need to update the flag definition in compose so you can use it multiple times |
Oh I see :) Any idea when this is gonna happen? |
sounds like a relatively easy one, any intention to add it soon? |
Multiple use of the |
That's great to hear @ndeloof - thanks (couldn't find a reference in the docs, but maybe I didn't looked hard enough) |
docker-compose --env-file=.env --env-file=.custom_env up -d
Doesn't seem to work but docker-run takes in multiple --env-file? I'd like to merge two env files and now only option seems to be: to include all variables in one env file.
The text was updated successfully, but these errors were encountered: