fix: make postgres port configurable for WSL2 compatibility

[Felipeness]

Summary

• Makes the Postgres host port configurable via DATABASE_PORT env var in packages/prisma/docker-compose.yml
• Defaults to 5450 for backward compatibility (${DATABASE_PORT:-5450}:5432)
• Adds documented DATABASE_PORT entry in .env.example with WSL2 troubleshooting context
• Follows existing pattern: root docker-compose.yml already uses ${REDIS_PORT:-6379}:6379 for Redis

Fixes #28395

Root cause

Docker Desktop on WSL2 has a known issue where its port-forwarding proxy retains stale reservations after unclean container exits. Since Cal.com hardcodes port 5450, users cannot work around the conflict without modifying tracked files. The error manifests as:

/forwards/expose returned unexpected status: 500

Test plan

• yarn dx works with default config (no DATABASE_PORT set) — port 5450 used
• yarn dx works with DATABASE_PORT=5451 set in .env — port 5451 used
• Verify .env.example has clear documentation about when to use DATABASE_PORT

[CLAassistant]

All committers have signed the CLA.

[cubic-dev-ai]

No issues found across 2 files

[cubic-dev-ai]

1 issue found across 1 file (changes from recent commits).

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="turbo.json">

<violation number="1" location="turbo.json:49">
P2: `DATABASE_PORT` was added to `globalEnv`, which makes it part of the hash for all Turbo tasks even though it appears to be only needed for local Prisma/docker-compose flows. This can unnecessarily reduce cache reuse across unrelated tasks.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}

[cubic-dev-ai]

1 issue found across 1 file (changes from recent commits).

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="turbo.json">

<violation number="1" location="turbo.json:338">
P2: `DATABASE_PORT` is only exposed to `@calcom/prisma#db-up`, but `@calcom/prisma#db-reset` also shells into `db-up` via nested scripts and will lose the variable in Turbo strict mode, causing fallback to default port.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}

[Felipeness]

@cubic-dev-ai addressed your feedback — moved DATABASE_PORT from globalEnv to task-specific env for db-up and db-reset. Should fix both the cache reuse concern and the strict mode variable loss.