Skip to content

⭐️⭐️⭐️ Open-source, self-hosted alternative to Linear and Plane. Project management and issue tracking where teams and AI agents work side by side to plan and ship products.

2.0 KB
Raw Blame
# ─────────────────────────────────────────────────────────────
# Environment for the API test suite (bun test). Separate from .env so tests
# never touch the dev database. `bun run setup` writes this file, creates the
# test database, and migrates it; copy it by hand only to set it up yourself.
#
# The tests are integration tests: they run the real Elysia app against a real
# Postgres and create real better-auth sessions. Point DATABASE_URL at a
# dedicated TEST database — the db reset helper empties every table between
# tests, so it must never point at the dev or prod database.
# ─────────────────────────────────────────────────────────────

# Dedicated test database next to the dev one on the same Postgres
# (docker-compose.dev.yml). The name must contain "test" — the reset helper
# refuses to run otherwise. Host, port and credentials match the dev database
# in the root .env; only the database name differs.
DATABASE_URL=postgres://itsaplan:itsaplan@localhost:5432/itsaplan_test

# better-auth. Any fixed value works for a throwaway test DB.
BETTER_AUTH_SECRET=test-secret-not-for-production-use-only
API_URL=http://localhost:3000
APP_URL=http://localhost:3001

# NODE_ENV gates the db reset helper (belt-and-suspenders with the db-name check).
NODE_ENV=test

# S3-compatible object store (RustFS) for the attachments feature test. The local
# dev RustFS from docker-compose.dev.yml serves this; its minio-init creates the
# bucket. Reuse the same values as root .env — the test only writes uuid-keyed
# objects and deletes what it creates.
S3_ENDPOINT=http://localhost:9000
S3_REGION=us-east-1
S3_BUCKET=planner-attachments
S3_ACCESS_KEY_ID=minioadmin
S3_SECRET_ACCESS_KEY=minioadmin

# Secret encryption key (AES-256-GCM) for stored provider API keys.
APP_ENCRYPTION_KEY=test-secret-not-for-production-use-only