docs: clarify bulk execution and startup checks in help

This commit is contained in:
lingkai5wu committed 2026-10-10 23:17:10 +08:00
1 parent bf8c941a1d
commit 87c4e5b2a9
1 file changed
+14 -7
+14 -7
View File
@@ -96,13 +96,20 @@ Stage configuration:
after [--parallel N] STACK... Add a late stage
exclude STACK... Exclude stacks from bulk operations
Each before/after declaration is one ordered stage; unlisted stacks form
the default stage. Lifecycle commands run before -> default -> after,
reversed for stop/down. A failed stage skips all remaining stages.
up/start/update wait for running/healthy services when waiting is enabled.
Services need healthchecks to verify readiness beyond the running state.
up/update validate every selected Compose configuration before making changes.
Numeric settings do not accept leading zeros.
Bulk execution (without STACK):
Each before/after declaration creates a stage, in declaration order.
Unlisted stacks form the default stage; excluded stacks are skipped.
up/start/restart/pull/update run before -> default -> after.
stop/down reverse the full stage order.
Stages run one at a time. Stacks within a stage run in parallel, limited
by max_parallel or that stage's --parallel setting.
A stage finishes all its stacks; any failure skips the remaining stages.
Startup checks:
up/update validate all selected Compose configurations before making changes.
up/start/update wait up to wait_timeout seconds for each stack to be ready.
Services with healthchecks must be healthy; other services must be running.
Set wait_timeout to 0 to disable waiting.
Config: $CONFIG_FILE
EOF