Environments & variables
Separate production and preview configuration, secrets, and deployment rules per project.
What an environment controls
- Branch or trigger rules — which Git references deploy here
- Environment variables — plaintext or secret values injected at build/runtime
- Live deployment selection — which successful deployment serves traffic for this environment’s hostnames
Secrets
Mark sensitive values as secrets in the dashboard so they are stored with tighter presentation defaults (masked in UI) and excluded from casual copying. Treat rotation as an operational habit—update values and redeploy.
Changing variables alone does not always restart containers; trigger a new deployment after updating configuration your process reads at startup.
Preview vs production
Use preview environments for pull-request style workflows where supported, and production for customer-facing domains. Align database attachments so previews never mutate production data unintentionally.