Command Line Tools
wheels deploy config
Print the fully-resolved deploy.yml config as YAML. Mustache interpolation is expanded; destination overlays are merged. Makes no network calls.
Synopsis
Section titled “Synopsis”wheels deploy config [--destination=<name>] [--config=<path>]| Flag | Description |
|---|---|
--destination=<name> | Overlay deploy.<name>.yml before printing. |
--config=<path> | Override config/deploy.yml. |
Output
Section titled “Output”Prints a YAML dump with four keys that matter at deploy time:
service: myappimage: myorg/myappservers: web: - 192.0.2.10registry: server: ghcr.io username: myorgFull per-role options, env merging, and accessory blocks are not emitted in Phase 1 — wheels deploy config is a deliberate subset focused on what most users want to verify (which hosts, which image, which registry).
When to use
Section titled “When to use”- Verify
--destinationoverlays apply the keys you expect. - Confirm
{{env.*}}resolves to the right values. - Diff against
kamal configduring a migration from Ruby Kamal.
Example
Section titled “Example”wheels deploy config --destination=staging