https://<app>.getfloo.app, with managed Postgres, signed-in users, and your own domain.
New to floo? Start with the Quickstart.
What your agent controls
floo builds theDockerfile in your repository. Add one that specifies the runtime for your app:
- The Go version that compiles the binary and the base image it runs on.
- System packages in the final image, such as
ffmpegor Chromium, each oneapk addline. - The build flags and the start command.
- More services from the same repository, such as a background worker or a cron job.
floo.app.toml. Store secrets outside git.
1. Add a Dockerfile
The module builds a single binary from the repository root. Match thegolang image to the go line in go.mod: an older image fails with go.mod requires go >= ....
Dockerfile
apk add --no-cache ffmpeg, on the same RUN line.
Read PORT and listen on all interfaces:
main.go
2. Initialize the floo config
Install the CLI and sign in:curl -fsSL https://getfloo.com/install.sh | bash, then floo auth login. An agent can run the same journey over the HTTP API instead, starting from getfloo.com/agents.md.
floo.app.toml
migrate subcommand (for example with goose and SQL files embedded with embed), then set migrate_command = "/server migrate" under [services.web]. It runs as a one-off job with the new image before traffic moves to it. A failed migration stops the deploy. Use expand-then-contract migrations to keep the schema compatible with both old and new code.
3. Connect the repo and deploy
floo builds from your GitHub repository, not local files, so commit first.floo deploy pushes the commit and waits until the dev URL is live. The first time, it stops with one link if the floo GitHub App can’t read the repository yet: a human opens it and installs the App on the account that owns the repository, then you run floo deploy again. See Give floo access to your GitHub repository.
floo deploy --hosted has floo host the repository. See Deploy without GitHub.
When it’s done:
Your Go app is live at
https://my-go-app.getfloo.app.Every git push origin main ships to dev.4. Add a Postgres database
floo.app.toml
MANAGED_CREDS_TO_WEB because the web service receives the database credentials. That is expected when the web service queries the database.
DATABASE_URL is injected into the runtime. pgx reads it as is, TLS settings included:
main.go
pgxpool.New connects on first use, so the server starts and answers while Postgres wakes. Dev and prod each get a separate Postgres database and credentials, with no shared state.
5. Add per-user auth
Setaccess_mode = "accounts" and floo handles sign-in:
floo.app.toml
- Redirects unauthenticated requests to a hosted login page.
- Validates the session cookie on every request.
- Injects identity headers into every request that reaches your Go server.
encoding/json to the imports:
floo dev --fixture-user (see section 7) or send the headers yourself with curl -H 'X-Floo-User-Email: you@example.com' .... Access modes and identity headers in full: App sign-in.
6. Add a custom domain
Declare the domain infloo.app.toml:
owner/repo with your GitHub repository. For a floo-hosted project, see Environments.
show prints, then watch
activation:
net/http serves every host by default. If you build absolute URLs, read the host from X-Forwarded-Host. DNS setup and troubleshooting: Custom domains.
7. Local development with dev credentials
dev_command locally with DATABASE_URL and readable env vars from the app’s dev environment: a real connection to your dev Postgres, with no credentials in your shell history. Write-only secrets are withheld; supply separate local values when needed. Prod credentials never reach a local session.
The database exists after the first deploy that declares [managed.default]. Before that deploy, floo dev starts without DATABASE_URL.
To test signed-in flows, add --fixture-user:
floo dev then puts a proxy in front of each accounts-mode service that injects the same X-Floo-User-* headers floo’s gateway adds in production. The output table shows the raw service URL and the auth-proxied URL; use the auth-proxied one for any path that reads identity headers.
Common gotchas
/healthzis reserved. floo’s edge intercepts that exact path. Use/healthor/livez.- Listen on
":"+port. floo cannot reach127.0.0.1. CGO_ENABLED=0for a static binary. A cgo build links against the build image’s glibc and fails to start on Alpine. If you need cgo, run the final stage ondebian:bookworm-sliminstead.- CA certificates in the final image. Without them, TLS to Postgres and outbound HTTPS calls fail with
x509: certificate signed by unknown authority. X-Forwarded-Proto. floo’s edge terminates TLS and forwardsX-Forwarded-Proto: https.r.TLSis alwaysnilinside the container.
Next steps
App sign-in
Identity headers, access policies, and access modes in detail.
Cron jobs
Run a subcommand of the same binary on a schedule.
Dockerfiles
Layer order for fast pushes and recommended multi-stage builds.
Production environments
Dev vs prod, promotion, env overrides.