Environment Variables
Overview
Section titled “Overview”Each project has its own set of environment variables, stored both in the SQLite database and as a .env file in the project workspace directory.
Adding Variables
Section titled “Adding Variables”On the project details page:
- Scroll to the Environment Variables section
- Enter a key and value
- Click Add
Variables are available to your build commands as standard environment variables.
How It Works
Section titled “How It Works”When you add an env var through the UI:
- It’s saved to the
project_envtable in the database - It’s written to
<working-dir>/<project-id>/.env - Before each deployment, the
.envfile is loaded into the process environment
Editing and Deleting
Section titled “Editing and Deleting”- Edit: Click on an existing variable to modify its value
- Delete: Remove a variable from both the database and the
.envfile
Common Use Cases
Section titled “Common Use Cases”NODE_ENV=productionDATABASE_URL=postgresql://user:pass@localhost:5432/mydbAPI_KEY=your-api-keyPORT=8080Security Notes
Section titled “Security Notes”- Env vars are stored in plain text in the database
- The
.envfile is readable by the user running the service - Never store secrets that require encryption — use a dedicated secrets manager for those
- The
.envfile is never committed to your repository (it lives in the workspace, not the cloned repo)