Skip to main content
Runs a one-shot command with a service’s managed env vars injected: a test suite against managed Postgres, a backfill script, or a migration against the dev database, without redeploying. floo run creates a short-lived dev session to fetch the service’s env vars (DATABASE_URL, PG*, REDIS_URL, and custom vars set via floo env), runs the command in the service’s directory, and tears the session down on exit. The command’s exit code propagates exactly, so a failing test suite returns non-zero. Write-only secrets are withheld from the dev session; supply them locally. FLOO_WITHHELD_SECRET_KEYS names the withheld keys for the selected service.
Everything after -- is the command, so its flags are not parsed by floo.

Flags

Examples

How it differs from floo dev

  • floo dev starts a long-lived local server bound to a port, with cross-service discovery so web can reach api at http://localhost:<port>.
  • floo run is portless and single-shot: env vars for the duration of the command, with no local server and no cross-service discovery.

Errors