wheels deploy app maintenance

Write the server-side maintenance marker. Pair with app live to clear it.

Synopsis

wheels deploy app maintenance --release=<v> [--role=<name>] [--destination=<name>] [--dry-run]

Flags

| Flag | Description | |------|-------------| | --release=<v> | Required by the same parser as the other app verbs. | | --role=<name> | Limit to one role. | | --destination=<name> | Overlay destination config. | | --dry-run | Print the commands without executing. |

Behavior

Emits touch /tmp/kamal-maintenance-<service> on every host in the targeted role(s). Your app is responsible for checking for the marker and serving a maintenance response — this verb only writes the file.

Phase 2 simplification

The Phase 2 port uses a marker-file convention rather than kamal-proxy's native maintenance mode. A follow-up will swap in native proxy-level maintenance for true out-of-band blocking — the file-based approach here assumes app-level cooperation.

Example

example

wheels deploy app maintenance --release=abc1234