Description
The database name in packages/prisma/docker-compose.yml does not match .env.example:
- docker-compose.yml:
POSTGRES_DB: "cal-saml"
- .env.example:
DATABASE_URL="postgresql://postgres:@localhost:5450/calendso"
On a clean setup with a fresh Docker volume, Prisma migrations target the calendso database which does not exist in the container — only cal-saml does.
Impact
This hits every new contributor on their first yarn dx run. The setup either:
- Silently succeeds if Postgres auto-creates the database (masking the issue)
- Fails opaquely with a connection error that does not clearly indicate the name mismatch
Combined with other first-run friction points, this degrades the onboarding DX significantly.
Proposed Fix
One-line change — align both to the same name:
# packages/prisma/docker-compose.yml
POSTGRES_DB: "calendso"
This matches .env.example, which is the canonical reference for contributors.
Related: #28106 reports this exact mismatch.