Skip to content

Environment Variables ​

Set variables when you add a service, or later under the service's Variable tab. Changes apply on the next deployment.

Raw editing ​

Click Edit Raw Variables to paste .env-style lines:

sh
NODE_ENV=production
API_URL="https://api.example.com"
# comments and blank lines are ignored

Built-in variables ​

Every service gets these, which you can reference in your own values with ${NAME}:

VariableValue
PORTThe service's first port
<PORT>_PORTEach port by its name, such as WEB_PORT
ZENAVO_<PORT>_DOMAINThe domain bound to that port, such as ZENAVO_WEB_DOMAIN
ZENAVO_<PORT>_URLhttps:// plus that domain
CONTAINER_HOSTNAMEThe service name

Sharing between services ​

A service can expose some of its variables to the rest of the project; databases do this for their connection details (Databases). Other services then reference them as ${NAME}.

Generated passwords ​

${PASSWORD} in a template becomes a random password the first time the project is saved, and stays the same afterwards.

Secrets ​

Variable values are encrypted at rest, hidden from team viewers, and redacted from build and runtime logs.

Not affiliated with Zeabur.