deploys - floo

floo deploys is for viewing and managing deploy history. To trigger a deploy, push to GitHub or use floo redeploy. To validate your config before pushing, use floo preflight.

How deploys are triggered

Deploys are config-as-code and git-driven. There is no separate CLI deploy step in the everyday flow.

Trigger	Result
`git push` to your default branch	Builds and deploys to the dev environment automatically.
Cut a GitHub release on your repo	Promotes the live dev build to production.
`floo releases promote`	The same promotion from the CLI. It creates the GitHub release for you when a repo is connected.
`floo redeploy --app <name>`	Re-runs the same image (e.g. after an env-var change), no rebuild.
`floo redeploy --rebuild --app <name>`	Forces a new build from the latest commit.

After floo apps github connect <owner/repo>, you almost never need to run a deploy command directly, push, and the build starts. Watch progress with floo deploys watch --app <name> or in the dashboard.

Subcommands

`floo deploys list`

List compact deploy history for an app, newest first. Build logs are not included; use floo deploys logs for a specific deploy.

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. If DEPLOY_ID is omitted, shows logs for the latest deploy.

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 in real-time. Waits for the deploy to finish and shows 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 deploy status summary. Emits the latest deploy’s id, commit, derived phase booleans (image_built / service_ready / host_bound), the gateway URL, and a recommended next command, without dumping build logs, runtime audit payloads, or env-var values. Built for agents and scripts that need to know “what state is the deploy in?” without risking secret exfiltration through verbose output.

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`

Rollback to a previous deploy.

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

Flag	Description
`--yes`	Skip the tier-2 confirmation prompt

JSON output

{
  "success": true,
  "data": {
    "deploys": [
      {
        "id": "e5f6g7h8-...",
        "status": "live",
        "url": "https://my-app.on.getfloo.com",
        "created_at": "2026-04-06T12:00:00Z"
      }
    ],
    "limit": 20,
    "next_cursor": "eyJ0cyI6...",
    "has_more": true
  }
}

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

​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