Minor: PostgreSQL Service Commented Out in Docker Compose

[AliiiBenn]

Priority

🟡 Minor - Infrastructure Consistency

Location

docker-compose.yml:31-42

Problem Description

The PostgreSQL service configuration exists but is commented out, while MongoDB (which isn't used) is active.

Issues

1. Inconsistent with Code

• Code uses PostgreSQL via @payloadcms/db-postgres
• Docker Compose uses MongoDB
• PostgreSQL is commented out

2. Misleading Comment

Suggests PostgreSQL is optional, but it's actually required.

3. Developer Confusion

• New devs see "uncomment to use postgres"
• May think MongoDB is the default
• Waste time debugging connection issues

Expected docker-compose.yml

Option 1: Only PostgreSQL (Recommended)

Remove MongoDB service entirely, uncomment PostgreSQL service.

Related Issues

• Critical: Build Errors Ignored in Production Configuration #4 - Docker Compose uses MongoDB (critical parent issue)
• Critical: Syntax Error in auth.ts Configuration #3 - .env.example has MongoDB reference

Steps to Fix

1. Remove MongoDB service entirely
2. Uncomment PostgreSQL service
3. Update depends_on to reference postgres
4. Remove misleading comments
5. Add healthcheck to PostgreSQL
6. Test docker-compose up works

Additional Context

This issue compounds #4. Together they make the Docker setup completely broken. Once both are fixed, developers will be able to use docker-compose up successfully.