Command Line Tools
wheels deploy accessory
Sidecar container lifecycle. Every accessory verb takes the accessory name as a positional argument (or all for fan-out) and targets the pinned host(s) for that accessory: wheels deploy accessory boot db.
| Verb | Purpose |
|------|---------|
| boot | First-time install + run. |
| reboot | Stop, remove, re-install. |
| start | docker start. |
| stop | docker stop. |
| restart | docker restart. |
| details | docker ps --filter. |
| logs | Tail accessory logs. |
| remove | Stop + remove the container. |
Common arguments and flags
Section titled “Common arguments and flags”| Argument / flag | Description |
|------|-------------|
| <name> | Required positional. Accessory name, or all to fan out. |
| --destination=<name> | Overlay destination config. |
| --dry-run | Print commands without executing. |
Omitting the name throws DeployAccessoryCli.MissingName. There is no --name= flag — the deploy parser ignores it, so --name=db also ends in DeployAccessoryCli.MissingName.
Relationship to wheels deploy
Section titled “Relationship to wheels deploy”Accessory verbs are not part of the rolling app deploy. wheels deploy leaves accessories alone — that's deliberate, so routine rollouts can't accidentally bounce your database. See Accessories.