Configuration

Environment variables

Every project reads its configuration from a .env file in the project root, based on a committed .env.example. Copy the example, then fill in values for your environment:

cp .env.example .env

Secrets

Never commit a filled-in .env file. All .env files are gitignored by default — only .env.example (with placeholder values) is committed to the repository.

Database projects

Projects that use a database (PostgreSQL, SQLite) typically expose a DATABASE_URL variable and a seed command to create an initial admin user:

npm run db:seed

Docker-based projects

For projects with a docker-compose.yml, environment variables can be set directly in a .env file next to the compose file, or passed via docker compose --env-file.