Variables
Define reusable key/value pairs and secrets available to all your projects.
Use variables for values that several Compose projects share, such as a domain name, timezone, or database password.
Add a variable
Section titled “Add a variable”- Go to Projects → Variables.
- Select Add Variable.
- Enter a Key and a Value. To add several at once, switch to Paste .env and paste
KEY=VALUElines. - Choose the scope: all agents, or specific ones.
- If the value is sensitive, turn on Secret.
- Optional: turn on Inject into all containers. See Substitution or injection.
- Click Add Variable.
Reference it in a project like any Compose variable, for example ${DOMAIN}.
Keys must be valid POSIX environment names: letters, digits, and underscores, not starting with a digit.
- Allowed:
DB_PASSWORD,_INTERNAL - Rejected:
db-password,2FAST
Substitution or injection
Section titled “Substitution or injection”By default, a variable is only used for ${VAR} substitution in Compose files. Containers don’t see it unless a service passes it on, for example environment: - DOMAIN=${DOMAIN}.
Turn on Inject into all containers to also add the variable to every container’s environment in every project. A service’s own environment value for the same key wins. Injected variables show an Injected badge in the table.
From the CLI, pass --inject to arcane-cli variables create or update.
Agent scoping
Section titled “Agent scoping”Each variable applies to all agents or to specific ones. The same key can have different values in staging and production. Each row shows its scope.
Secrets
Section titled “Secrets”A Secret is encrypted in the database. Arcane masks it in the table, leaves it out of search, and never returns it to the browser.
Secrets are encrypted in the database and in transit, but written as plaintext to .env.global so Compose can read them. Protect that directory on the destination host.
What Compose can see
Section titled “What Compose can see”Arcane syncs variables from its database to each environment’s .env.global. On first sync, it imports the remote environment’s existing variables before managing the file.
Compose resolves ${VAR} from three places. Later ones win:
- Arcane’s own process environment, but only
TZ,LANG,LANGUAGE, andLC_ALL. .env.global, which the Variables page writes.- The project’s own
.env.