Environment Variables

Environment variables let you configure your application without committing secrets to your repository. Atlasflow scopes every variable to either build or runtime.

# Build vs runtime

A variable set as build is available to your Dockerfile or auto-detected build, but is not present in the running container unless you also add it as a runtime variable. A runtime variable is injected into the container's environment when it starts.

# Add a variable

1. Open your project Settings.
2. Choose the Build or Runtime variables section.
3. Add the variable name and value.
4. Save. The change applies to your next deployment.

# Security

Values are encrypted at rest. The dashboard hides values by default; you can reveal a variable's value when you need to confirm it. Avoid logging secret values from your application.

# Updating and removing

Editing or deleting a variable takes effect on the next deployment. Trigger a redeploy if you want a change to apply immediately without pushing a commit.

# Reserved behavior

Atlasflow injects the variables your container needs to run on the platform. Define your own application variables as usual; if a name you choose ever conflicts with a platform value, the platform value takes precedence.

# Next steps

• Configuration: other project settings.
• Redeploys: apply variable changes immediately.
• Builds: how build variables are used.