Support for compose environment variables and interpolation #532
Milestone
Comments
diegocastrum
added a commit
to diegocastrum/django-celery-beat
that referenced
this issue
Apr 11, 2022
Added `.env` to `.gitignore`. Added a `.env.sample` that will be used by anyone he need it. Just copy it as `.env` in your local devel env and use the (supported) variables you need. `docker-compose.yml` updated in order to support string interpolation when using variables defined in a `.env` file. Fixed a typo in `issue_template.md`.
auvipy
added a commit
that referenced
this issue
Apr 11, 2022
* Added support for compose env vars (#532) Added `.env` to `.gitignore`. Added a `.env.sample` that will be used by anyone he need it. Just copy it as `.env` in your local devel env and use the (supported) variables you need. `docker-compose.yml` updated in order to support string interpolation when using variables defined in a `.env` file. Fixed a typo in `issue_template.md`. * newline * newline Co-authored-by: Asif Saif Uddin <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary:
To avoid port collision when working on
django-celery-beatin some devel environments it would be nice if thedocker-composemakes use of env variables defined in a.envfile, for more information about how docker-compose loads these variables take a look of the docker-compose documentation.Detailed information
The idea is just to make use of string interpolation from
docker-compose.ymltaking the current values that everybody uses as defaults, When the project runs, if a.envfile is found with the right env var defined, docker-compose will use it instead the default one. This approach shouldn't any current development setupThe text was updated successfully, but these errors were encountered: