redeploy

git push is the primary deploy flow. Use floo redeploy only to redeploy without a code change, for example after updating env vars or changing access mode. By default it rolls out the previous image again with fresh env and config; --rebuild builds the current default-branch commit again.

Redeploy an app that already has a dev deploy. It cannot run the first deploy; that comes from a push to the connected branch.

floo redeploy [PATH]

Arguments

Argument	Description	Default
`PATH`	Project directory	`.` (current directory)

Flags

Flag	Description
`--app APP`	Existing app name or UUID to deploy to
`--service NAME`	Deploy only specific services (repeatable or comma-separated)
`--rebuild`	Build the exact current GitHub default-branch commit again (re-downloads source and runs the build). If a restart reports an unavailable immutable contract, run the exact `--rebuild` command it returns.
`--sync-env`	Re-sync env vars from configured `env_file` before deploying. Silently ignored with `--app`; cannot be combined with `--service` (`INVALID_ARGUMENTS`).
`--skip-migrations`	Declare that no migrations are pending and skip the MIGRATE step. The deploy records MIGRATE as `SKIPPED`, not `SUCCESS`, so the audit trail is unambiguous. Meaningful only with `--rebuild`; a restart already skips MIGRATE because the image was migrated before, and `--app` without `--rebuild` rejects the flag (`CONFIG_INVALID`). If you are wrong, the new image boots against an unmigrated schema.
`--preflight`	Preview the redeploy without applying it

Examples

# Redeploy current directory
floo redeploy

# Redeploy a specific app
floo redeploy --app my-app

# Rebuild the current default-branch commit
floo redeploy --rebuild --app my-app

# From the project directory, re-sync env_file before redeploying
floo redeploy --sync-env

# Hotfix rebuild with no pending migrations
floo redeploy --rebuild --skip-migrations --app my-app

# Preview without applying
floo redeploy --app my-app --preflight

# Redeploy only specific services
floo redeploy --service api --service web

# Agent workflow: redeploy and extract URL
floo redeploy --json 2>/dev/null | jq -r '.data.deploy.url'

What happens

Preflight (only without --app): validates config, checks ports, service names, env files, and Dockerfiles
API: sends the deploy request to the floo API
Managed Services: reconciles any missing declared Postgres, Redis, or Storage resources
Image selection: without --rebuild, reuses the previous immutable image; with --rebuild, pulls the exact current GitHub default-branch commit and runs the build
Deploy: rolls out the selected image with fresh config and env state
URL: the live URL is returned

Source is always pulled from GitHub. Code is never uploaded from your machine.

JSON output

{
  "success": true,
  "data": {
    "app": {
      "id": "a1b2c3d4-...",
      "name": "my-app",
      "status": "live",
      "url": "https://my-app.getfloo.app"
    },
    "deploy": {
      "id": "e5f6g7h8-...",
      "status": "live",
      "url": "https://my-app.getfloo.app",
      "build_logs": "..."
    },
    "detection": {
      "runtime": "nodejs",
      "framework": "Next.js",
      "version": "^14.0.0",
      "confidence": "high"
    },
    "services": ["web"]
  }
}

Errors

Code	Meaning
`NOT_AUTHENTICATED`	Run `floo auth login` first
`INVALID_PATH`	Path is not a valid directory
`NO_CONFIG_FOUND`	No `floo.app.toml` found. Run `floo init` first
`CONFIG_INVALID`	Preflight validation failed
`APP_NOT_FOUND`	The `--app` value doesn’t match any existing app
`DEPLOY_FAILED`	Build or deploy failed. Check build logs
`DEPLOY_TIMEOUT`	Deploy timed out after 10 minutes

CLI

Config and runtime

Errors

API

Arguments

Flags

Examples

What happens

JSON output

Errors

​Arguments

​Flags

​Examples

​What happens

​JSON output

​Errors

Arguments

Flags

Examples

What happens

JSON output

Errors