fix: database Compose warnings and set a project name #3701
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.
Thanks for submitting a PR! Please check the boxes below:
pre-commit
to check lintingdocs/
if required so people know about the feature!Changes
Fixes two warnings when launching the database from Docker Compose:
Also, this PR adds a top-level
name
field to the Compose file. Otherwise, the default project name isdocker
(the directory name where the Compose file lives), which is not very informative.Before:
After:
More details on the top-level
version
andname
Compose field names: https://docs.docker.com/compose/compose-file/04-version-and-name/How did you test this code?
Manually tested by starting the database using Compose as usual: