Environment variables

Configure secrets and runtime settings for each deployment from the dashboard.

Environment variables are available to your app at build and/or runtime depending on the framework. Set them in Renboot instead of committing secrets to Git.

Add variables when creating a project

In New Deployment, use the env editor: add rows with KEY and value.
Or paste a block of KEY=value lines (one per line) and merge them into the form.

DATABASE_URL=postgres://user:pass@host:5432/db
NODE_ENV=production
NEXT_PUBLIC_SITE_URL=https://my-app.renboot.com

Edit on an existing deployment

Open the deployment or instance detail page → Environment (or Env) tab. Add, update, or remove keys, then save. Restart or redeploy so the running app picks up changes.

Best practices

Never commit production secrets to the repository.
Prefer different values per environment (production vs staging).
Rotate keys if they may have leaked; update them here and redeploy.
Client-visible keys (e.g. NEXT_PUBLIC_*) are not secret — treat them as public.

Security

Values are stored securely and are not shown in public list views. Only people with access to your Renboot account (or team) can manage them.

Related: Create a deployment