Skip to main content
The script downloads the release for your platform, checks its SHA-256, and installs floo to /usr/local/bin. If that directory is not writable, it asks for sudo.

​
Supported platforms

​
Install options

Set these before bash:
Pin a version in CI so a new release cannot change a pipeline mid-run.

​
Sign in

The CLI opens your browser to finish sign-in and stores a key in ~/.floo/config.json. For CI and other machines without a browser, use a floo API key; see floo API keys.

​
Keep it updated

floo version checks for a newer release and installs it. Releases are date-versioned, such as 2026.10.27. Set FLOO_NO_UPDATE_CHECK=1 to skip the check. See update.

​
Tools floo works alongside

  • git, to commit and push. floo deploys from GitHub, never from your working directory.
  • The GitHub CLI (gh), optional, to publish prod releases with gh release create. The GitHub web UI works too; see Environments.
  • Docker, optional, only to test your image locally. floo builds the image for you.

​
Next steps

Quickstart

Connect a repo and get a live dev URL.

CLI overview

Every command group and the JSON output contract.