fix: Make db service use correct env file #15659
Merged
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.
Point the db service to docker/.env-non-dev instead of docker/.env.
SUMMARY
The docker-compose.non-dev.yml db service is pointing to the docker/.env file when it should point to the docker/.env-non-dev file.
TESTING INSTRUCTIONS
Run the docker compose service and see that it picks up the environment variables in docker/.env-non-dev instead of docker/.env.
ADDITIONAL INFORMATION