Skip to main content
For your GitHub repository, publish a GitHub release to deploy its commit to prod once it is live in dev. For a floo-hosted project or an app with no repository, use floo promote. See Production environments for the release flow. floo deploys --env prod lists prod deploys with the release each one shipped: tag, number, who promoted it and the image.

floo promote

Release the latest live dev deploy to prod for a floo-hosted project or an app with no repository. For a floo-hosted project, floo also publishes a GitHub release on its repository. An app connected to your own GitHub repo is refused with PROMOTE_USE_GITHUB_RELEASE. The command returns the tag and release URL; floo deploys --app my-app --env prod tracks the background deploy and shows the release it shipped.

What happens during promote

  1. Image selection. Promote deploys the images from the latest live dev deploy. It rebuilds only when the prod environment has a build-time env var (VITE_*, NEXT_PUBLIC_*, or REACT_APP_*); then each service is built again from the source deploy’s archived source with the prod values as build arguments.
  2. Migrations. Each declared migrate_command runs as a one-off job with prod env vars before traffic shifts. A failure stops promotion and leaves the previous live revision serving. Keep the old code compatible with schema changes through expand-then-contract migrations. floo deploy --rebuild --skip-migrations has no effect on promote.
  3. Routes. floo updates routes on the shared app host and per-service hosts, including routes affected by a service rename.
  4. Access grants. The gateway is granted invoke access on public services, and the app identity on internal services.

Flags

Examples

JSON output

release_url is set for floo-hosted projects and null for an app with no repo.

rollback

Use floo rollback to restore a previous live deploy’s image without rebuilding:
The app and deploy ID are positional arguments. --preflight previews the operation; --yes is required in non-interactive runs. Rollback keeps current environment configuration and does not undo database migrations.

Errors