domain: kamal-deploy.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Create config/deploy.yml with the required service (container name prefix) and image (Docker image name) keys
Add servers: to list deployment hosts (optionally split into roles), and registry: for the Docker registry credentials
Add env: for environment variables and builder: for build architecture/secrets configuration
Optionally configure accessories:, proxy: (kamal-proxy settings), and logging:
Use kamal deploy -d <destination> to layer config/deploy.<destination>.yml on top of the base file for multi-environment setups
Known gotchas
Kamal rejects unrecognized top-level keys outright — typos fail loudly unless the block is prefixed with x- to mark it as an intentionally-ignored extension
primary_role defaults to web; if your app has no web role you must set primary_role explicitly or Kamal's proxy/health-check assumptions break
retain_containers defaults to 5 and deploy_timeout to 30 seconds — both are commonly under-tuned for slow-booting apps
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?