docs: clarify that custom compose command replaces the default instead of appending#165
Merged
Merged
Conversation
…d of appending The docs claimed the Command field appends to the default command, but createCommand in dokploy fully replaces it with the custom command. Update both pages to describe the override behavior. Fixes #142 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
1 participant
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.
Summary
The docs claimed the compose
Commandfield appends to the default command, butcreateCommandin dokploy fully replaces it with the custom command (executed asdocker <command>). The UI already describes it correctly as an override.This updates both pages that mentioned the append behavior:
core/features.mdx: now describes the field as a custom command that fully replaces the default one.core/docker-compose/index.mdx: now explains the replacement behavior, that the command always starts withdocker, and shows an example of a full custom command with--force-recreate.Fixes #142
🤖 Generated with Claude Code