Conversation
This file contains hidden or 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.
In #334 we were using
COMPOSE_FILEenv-var, same as-f/--filecli arg to use multiple compose files in our profile folders (explicit, study, suite, ...).Problem: the bind mounts path to local paths is sensitive from where we do the
docker compose ...commands (look withdocker compose config).Solution: the
includefeature (howtos) since Docker Compose v2.20.0 permit to modularise file with the paths always resolved from the yaml where it declared, not from the current directory (pwd).Verifying:
The config files has also been reorganized per service for easier management.
I also use this version since two months now without problems.