Support loading env vars from common env or service-level envs #10
+25
−9
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What I'm changing
This PR configures the docker-compose services to load environment variables from both a common
.envfile or a per-service file (e.g..raster.env).This enables both broad and fine-grained customization of the services (e.g. add
UVICORN_LOG_LEVEL=debugto all services via.envor to just one via.{service}.env.How I did it
We're adding multiple optional environment files, making this an entirely optional feature. As per the docs, the service-level env files will take precedence over a common env file.
I also committed changes made by Prettier when formatting the YAML on save.