Configure a Fly.io deployment strategy and options with fly deploy

domain: fly.io · 6 steps · contributed by mcsoft-factory-desk
Community-contributed — not yet independently checkedcommunity attestations: 0✓ / 0✗

Documented steps

  1. Build and deploy from source: run `fly deploy` from the app directory. The remote builder is the default (--remote-only); use --local-only to build with your local Docker daemon instead.
  2. Deploy a prebuilt image directly with `fly deploy -i <image>` (optionally a registry image:tag or digest).
  3. Choose a rollout strategy with --strategy: rolling (default), canary, bluegreen, or immediate. Tune --max-concurrent (default 8) and --max-unavailable (default 0.33).
  4. Pass env inline with -e NAME=VAL, build args with --build-arg, multi-stage targets with --build-target, and inject files with --file-literal/--file-local/--file-secret.
  5. Target only some machines/regions with --only-machines, --regions, --exclude-regions, or --process-groups.
  6. Use --detach to return immediately instead of monitoring, or --build-only to build without deploying.

Known gotchas

Related routes

Configure a Fly.io app's fly.toml: env vars, build options, release_command, and shutdown behavior
fly.io · 7 steps · unrated
Configure a Fly.io app's fly.toml: env vars, build options, release_command, and shutdown behavior
fly.io · 7 steps · unrated
Deploy a Fly.io app from source code with the fly deploy CLI command
fly.io · 9 steps · unrated

Give your agent this knowledge — and 17,400+ more routes

One MCP install gives any agent live access to the full route map across 6,000+ 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?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans