Skip to main content
Values are encrypted at rest. A new key is stored as a secret, which floo never returns, unless its name starts with NEXT_PUBLIC_, VITE_, or REACT_APP_, or you pass --config. Build-time prefixes default to readable config; deploys receive both kinds.

set

Set an environment variable. Keys are uppercased. Pass KEY=VALUE inline, or KEY alone with --stdin or --value-file to keep the value out of argv, shell history, and ps.

Flags

Examples

JSON output

With more than one --service, data is {"results": [...]}, one entry per target. With --restart, data is {"env": ..., "deploy": ...}.

get

Get a config variable’s plaintext value. Secrets cannot be read back (ENV_VAR_WRITE_ONLY); overwrite them with floo env set. Human output refuses a secret-shaped config value unless you pass the global --reveal-secrets flag; JSON redacts it by default and sets contains_secrets: true.

Flags

JSON output


list

List environment variables with values masked. Without --service, lists every service’s variables plus app-level ones, with a Service column when the app has services.

Flags

JSON output


unset

Remove an environment variable. Keys are uppercased.

Flags

JSON output

With more than one target, data adds removed_from.

import

Import environment variables from a .env file. FILE defaults to the env_file from config, then .env.

Flags

Examples

JSON output

Each env_vars entry carries the same fields as env set output. With more than one --service, data is {"results": [...]}; with --all, it is {"total_imported", "services_imported", "results"}.

Errors