Environment Variables
Configuring your app at runtime with environment variables, and uploading a .env file.
Environment variables are key/value pairs injected into your App's container. Use them for anything your app reads from its environment at runtime — database URLs, third-party API keys, feature flags, ports, whatever your framework expects.
Setting them
From your App's Environment Variables page, add or edit variables one at a time, or paste/upload a .env file (KEY=VALUE per line, # comments and quoted values supported) to set several at once.
Setting a variable that already exists updates its value in place; setting a new key creates it. Variables you don't touch are left alone — this is additive, not a full replace. You can also edit or delete a single variable directly, without touching the rest.
When changes take effect
Only on your next deploy. A running container's environment is fixed at the moment it starts — Raklane doesn't live-reload environment variables into containers that are already running. If you change a variable and want it to take effect immediately, trigger a redeploy (see Deploying Your App).
Deleting a variable
Remove it from the Environment Variables page. Like changes, a deletion only takes effect on the app's next deploy.
Environment variables vs. secrets
Environment variables are for your app's regular configuration. If a value is sensitive credentials for something Raklane itself needs (a private repo token, a webhook signing key) rather than something your app reads, it belongs in Secrets instead.