flyctl deploy

Deploy Fly applications

Options

NameDescription
--app, -a <app>Application name
--build-arg <build-arg>Set of build time variables in the form of NAME=VALUE pairs. Can be specified multiple times
--build-onlyBuild but do not deploy
--build-target <build-target>Set the target build stage to build if the Dockerfile has more than one stage
--config, -c <config>Path to application configuration file
--detachReturn immediately instead of monitoring deployment progress
--dockerfile <dockerfile>Path to a Dockerfile. Defaults to the Dockerfile in the working directory
--env, -e <env>Set of environment variables in the form of NAME=VALUE pairs. Can be specified multiple times
--image, -i <image>The image tag or ID to deploy
--image-label <image-label>Image label to use when tagging and pushing to the fly registry. Defaults to "deployment-{timestamp}"
--local-onlyOnly perform builds locally using the local docker daemon
--nixBuild with Nix
--no-cacheDo not use the build cache when building the image
--nowDeploy now without confirmation
--pushPush image to registry after build is complete
--region, -r <region>The region to operate on
--remote-onlyPerform builds on a remote builder instance instead of using the local docker daemon
--strategy <strategy>The strategy for replacing running instances. Options are canary, rolling, bluegreen, or immediate. Default is canary, or rolling when max-per-region is set