CUSTOM_UP_COMMAND and SERVICE_UP_ONLY #178
Open
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.
Two additions:
CUSTOM_UP_COMMAND
If
CUSTOM_UP_COMMANDis included in.compose-cd, then instead of running the normaldocker compose up -dcommand within the directory, an alternate command can be supplied.This is useful when using a secrets manager or injecting other .envs.
Documentation on this use case has been added to the
README.md.SERVICE_UP_ONLY
If
.compose-cdincludesSERVICE_UP_ONLY=true, then docker compose will not bring down the containers.This is useful for example if you are running traefik as a compose-cd managed stack, and it is also used to expose the secrets store (Vault, 1Password Connect, etc.. If you take the stack down then compose-cd will be unable to resolve the secrets needed to bring it back online.