fix: use percent-encoded DATABASE_URL instead of split DB_PASSWORD trick

Drizzle ORM mutates client.options (parsers/serializers) after the postgres
client is created, which causes the separately-passed password option to be
lost on the actual connection attempt. Root cause confirmed on VPS: raw
postgres.js query succeeded while drizzle.execute() failed with auth error.

Fix: encode the password directly in DATABASE_URL (%23 = #, %5D = ], %3D = =).
postgres.js decodes percent-encoding correctly. No separate DB_PASSWORD env
var needed in the app container anymore.

DB_PASSWORD is still used by the Postgres container (POSTGRES_PASSWORD).
Coolify env var to set: DATABASE_URL=postgres://wc:<encoded-pass>@db:5432/worldcup

Also adds resolver-level isMissingTable() guards so the app returns empty
results instead of GraphQL errors on a fresh deploy before sync runs.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
2026-06-14 17:01:06 +02:00
parent 2b22f504cf
commit 0eb0fb5ee4
5 changed files with 106 additions and 88 deletions
+1 -2
View File
@@ -6,8 +6,7 @@ services:
db:
condition: service_healthy
environment:
DATABASE_URL: postgres://wc@db:5432/worldcup
DB_PASSWORD: ${DB_PASSWORD}
DATABASE_URL: ${DATABASE_URL}
NODE_ENV: production
labels:
- "traefik.enable=${TRAEFIK_ENABLED:-false}"