Skip to main content
Use this guide when you need to add secrets, inspect injected values, or target env vars at one service in a multi-service app.

​
1. Set a Value

floo env set DATABASE_URL=postgres://user:pass@host:5432/db --app my-app
floo env set API_KEY=secret --app my-app --restart
Use --restart when the running app needs the new value immediately.

​
2. Inspect Values

Use masked output when you only need confirmation: 
floo env list --app my-app
Use plaintext output when you need the actual value: 
floo env get DATABASE_URL --app my-app
That env get path is part of the shipped CLI surface, so do not document env vars as readable only from inside the container.

​
3. Scope to Specific Services

In multi-service apps, target specific services. Most commands use --services (plural, repeatable). env get uses --service (singular) since it returns one value. 
# Backend secrets — api/worker only
floo env set DATABASE_URL=postgres://... --app my-app --services api
floo env set API_KEY=secret --app my-app --services api --services worker

# Frontend config — web only (public values only)
floo env set VITE_API_URL=https://my-app.getfloo.com/api --app my-app --services web

# Inspect per service
floo env list --app my-app --services api
floo env get DATABASE_URL --app my-app --service api
floo env import ./api/.env --app my-app --services api
Never set backend secrets (DATABASE_URL, API keys, tokens) on frontend services. Build-time variables (VITE_*, NEXT_PUBLIC_*, REACT_APP_*) are baked into the JS bundle and visible to end users. Always use --services to target backend-only services when setting secrets.
Scoping rules:
  • Single-service app: env vars go to the only service (no --services needed)
  • Multi-service app, 1 service deployed: auto-targets that service
  • Multi-service app, 2+ services: --services is required, CLI errors without it
Managed service env vars (DATABASE_URL, REDIS_URL, STORAGE_BUCKET) are provisioned at app scope and available to all services by default.

​
4. Import From Files

floo env import .env --app my-app
floo env import --all --app my-app
Use --all when you want Floo to import from the configured env_file paths across services. 
floo env list --app my-app
floo env get API_KEY --app my-app
floo logs --app my-app --error --since 30m
floo redeploy --restart --app my-app

​
For Agents

floo env set DATABASE_URL=postgres://... --app my-app --json
floo env list --app my-app --json 2>/dev/null | jq '.data.env_vars'
floo env get DATABASE_URL --app my-app --json 2>/dev/null | jq '.data.value'

CLI Reference

See the exact env set, env get, env list, env remove, and env import flags.