deploys

floo deploys views and manages deploy history. To deploy, push to GitHub, run floo deploy from a local git repository, or use floo redeploy; to validate config before pushing, use floo preflight.

How deploys are triggered

Deploys are config-as-code and git-driven: every deploy traces back to a commit.

Trigger	Result
`git push` to your default branch	Builds and deploys to the dev environment automatically.
`floo deploy` in a local git repository	Pushes the current commit to a floo-hosted project (creating it on the first run) and waits until it is live in dev.
`gh release create <tag> --repo <owner/repo>` on your repo	Deploys the release’s commit to production once it is LIVE in dev.
`floo releases promote`	Deploys the latest LIVE dev deploy to production for a floo-hosted project or an app with no repo. Refused for your own GitHub repo.
`floo redeploy --app <name>`	Re-runs the same image (for example after an env-var change), no rebuild. Needs an existing dev deploy.
`floo redeploy --rebuild --app <name>`	Rebuilds the current GitHub default-branch commit.

After floo apps github connect <owner/repo>, a push starts the build. For a floo-hosted project, floo deploy or a push to its floo remote does. Watch progress with floo deploys watch --app <name> or in the dashboard.

Subcommands

`floo deploys list`

List compact deploy history, newest first, without build logs; use floo deploys logs for those.

floo deploys list --app my-app
floo deploys list --app my-app --limit 50 --cursor eyJ0cyI6...

Flag	Description
`--app APP`	App name or UUID
`--limit N`	Maximum rows to return (default `20`)
`--cursor CURSOR`	Continue from a previous response’s `next_cursor`

When more rows exist, human output ends with the exact floo deploys list ... --cursor command for the next page, and JSON output carries next_cursor and has_more.

`floo deploys logs [DEPLOY_ID]`

Show build logs for a deploy, or the latest deploy when DEPLOY_ID is omitted.

floo deploys logs abc123 --app my-app
floo deploys logs abc123 --app my-app --follow

Flag	Description
`--app APP`	App name or UUID
`--follow`	Stream logs in real-time for active deploys

`floo deploys watch`

Stream deploy progress until the deploy finishes, with build logs as they arrive.

floo deploys watch --app my-app
floo deploys watch --app my-app --commit abc1234

Flag	Description
`--app APP`	App name or UUID
`--commit SHA`	Match a deploy by commit SHA prefix (waits up to 120s)

`floo deploys status`

Print a compact, agent-safe status summary of a deploy: id, commit, derived phase booleans (image_built / service_ready / host_bound), the gateway URL, a recommended next command, and deploy diagnostics. It never includes build logs, runtime audit payloads, or env-var values, so an agent can check deploy state without risking secret exfiltration. image_built is true when the build step succeeded, false when it was skipped (for example, a restart that inherits the image), and null when evidence is missing or inconclusive. duration_ms covers the whole deploy attempt, including scheduling and rollout.

floo deploys status --app my-app
floo deploys status --app my-app --id e5f6g7h8 --json

Flag	Description
`--app APP`	App name or UUID
`--id ID`	Deploy ID. Defaults to the latest deploy for the app
`--json`	Machine-readable output for agents

`floo deploys rollback APP DEPLOY_ID`

Roll back to a previous deploy. It needs confirmation: interactive mode prompts y/N; non-interactive runs require --yes.

floo deploys rollback my-app abc123
floo deploys rollback my-app abc123 --yes --json

Flag	Description
`--yes`	Skip the `y/N` prompt. Required in non-interactive contexts.
`--preflight`	Preview the rollback without applying it

JSON output

{
  "success": true,
  "data": {
    "deploys": [
      {
        "id": "e5f6g7h8-...",
        "status": "live",
        "url": "https://my-app.getfloo.app",
        "created_at": "2026-04-06T12:00:00Z",
        "started_at": "2026-04-06T12:00:02Z",
        "finished_at": "2026-04-06T12:02:37Z",
        "duration_ms": 155000,
        "failure_reason": null,
        "failing_stage": null,
        "triggered_by": "github_push",
        "commit_sha": "abc1234...",
        "env": "dev"
      }
    ],
    "total": 42,
    "page": 1,
    "per_page": 20,
    "limit": 20,
    "next_cursor": "eyJ0cyI6...",
    "has_more": true
  }
}

triggered_by is one of:

Value	Started by
`github_push`	A push to the connected branch
`github_release`	A GitHub release on your repo
`github_pr`	A pull request’s preview
`promote`	`floo releases promote`
`restart`	`floo redeploy` without `--rebuild`, or `floo env set --restart`
`rollback`	`floo deploys rollback`
`cli`	`floo redeploy --rebuild`, or `POST /v1/apps/{app_id}/deploys`

The deploy API (GET /v1/apps/{app_id}/deploys) also returns reconciled_to_head. It is true when floo started the deploy itself to bring dev back to the latest commit on your default branch, for example after a push arrived while another deploy was running. Its triggered_by still reads github_push, and the dashboard labels it Auto redeploy.

Errors

Code	Meaning
`NOT_AUTHENTICATED`	Run `floo auth login` first
`APP_NOT_FOUND`	The `--app` value doesn’t match any existing app
`DEPLOY_NOT_FOUND`	The deploy ID doesn’t match any deploy for this app

CLI

Config and runtime

Errors

API

How deploys are triggered

Subcommands

`floo deploys list`

`floo deploys logs [DEPLOY_ID]`

`floo deploys watch`

`floo deploys status`

`floo deploys rollback APP DEPLOY_ID`

JSON output

Errors

​How deploys are triggered

​Subcommands

​floo deploys list

​floo deploys logs [DEPLOY_ID]

​floo deploys watch

​floo deploys status

​floo deploys rollback APP DEPLOY_ID

​JSON output

​Errors

How deploys are triggered

Subcommands

`floo deploys list`

`floo deploys logs [DEPLOY_ID]`

`floo deploys watch`

`floo deploys status`

`floo deploys rollback APP DEPLOY_ID`

JSON output

Errors