Command Line Tools
wheels deploy init
Scaffold the files wheels deploy reads: config/deploy.yml and .kamal/secrets. Also creates .kamal/hooks/ (empty) for optional hook scripts.
Synopsis
Section titled “Synopsis”wheels deploy init [--service=<name>] [--image=<path>] [--registry-username=<user>] [--force]| Flag | Description |
|---|---|
--service=<name> | Service name to bake in. Defaults to the project directory basename. |
--image=<path> | Image path. Defaults to <service>/web. |
--registry-username=<user> | Registry username. Defaults to changeme — you’ll edit it. |
--force | Overwrite existing files. Without this, an existing config/deploy.yml aborts with DeployMainCli.InitAlreadyExists. |
What it creates
Section titled “What it creates”config/deploy.yml— a starter manifest withservice,image,servers,registry,envstubs..kamal/secrets— key/value placeholders for the registry password and any app secrets..kamal/hooks/— empty directory. Drop executablepre-deploy,post-deploy, orpost-deploy-failurescripts here later.
Add .kamal/secrets* to .gitignore before running.
Example
Section titled “Example”wheels deploy initwheels deploy init --service=myapp --image=ghcr.io/myorg/myapp --registry-username=myorgAfter running, edit both files — see Your First Deploy for the walk-through.