Environment variables

Edit Variables on a Service, save, and redeploy so runtime picks up new configuration.

Written By Zoro

Last updated 3 days ago

Runtime configuration for App and Docker Services

lives in the Variables tab (the URL may use tab=environment). Values apply on the next successful Deployment after you Save.

Database Services in the applications flow do not expose the same Variables tab; connection details and exposure are handled on Overview, Deployments, and Backups. For variable syntax and reference types, see Service settings under Services in the sidebar.

Prerequisites

  • Permission to edit the Service.
  • You understand which values are secrets (never paste production secrets into chat or tickets).

Change variables

  1. Open the Application → Environment → Service.
  2. Open the Variables tab. The heading title is Variables.
  3. Add, edit, or remove rows (keys and values) using the in-product controls. Use Service settings under Services in the sidebar for static values, references to other Services, secret(), and combined strings.
  4. Save your changes.
  5. Go to Deployments and run Deploy or Redeploy so the new configuration is applied on the Worker Node.

Expected outcome: After the deployment succeeds, the running Service processes see the updated environment. While variables are being reconciled, deploy-related actions may be briefly disabled; they re-enable when the product finishes updating populatedVariables.

Importing from .env

The Variables tab can offer Import .env file (or equivalent). Use it for bulk entry, then review keys, Save, and Redeploy.

Screenshots

Recommended captures:

  • Variables tab with a few example rows (use fake values).
  • Save and the Deployments tab with Redeploy highlighted after a variable change.

Related