gitadmin/INSIGHT-MVP
1
0
Fork 0
mirror of http://172.20.10.11:3000/gitadmin/INSIGHT-MVP.git synced 2026-06-25 00:16:41 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions

fix(crm): use direct postgres connection instead of pgbouncer

Browse source 
PgBouncer in transaction pool mode strips the search_path startup
parameter, which Prisma needs for the app_crm schema. CRM now
connects directly to PostgreSQL.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Thomas Reitz 2026-03-10 16:34:56 +01:00
parent 86e5d36e98
commit aa5fc2e44d
2 changed files with 5 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
.env.example
View file

@ -84,5 +84,7 @@ AZURE_REDIRECT_URI=https://172.20.10.59/api/v1/auth/sso/microsoft/callback
# CRM-Service (packages/crm-service)
# ============================================================
CRM_APP_PORT=3100
CRM_DATABASE_URL=postgresql://${DB_USER}:${DB_PASSWORD}@pgbouncer:5432/${DB_NAME}?schema=app_crm
# PgBouncer (transaction mode) kann search_path nicht weiterleiten,
# daher nutzt CRM direkt PostgreSQL (nicht PgBouncer)
CRM_DATABASE_URL=postgresql://${DB_USER}:${DB_PASSWORD}@postgres:5432/${DB_NAME}?schema=app_crm
CRM_DATABASE_URL_DIRECT=postgresql://${DB_USER}:${DB_PASSWORD}@postgres:5432/${DB_NAME}?schema=app_crm

3
docker-compose.crm.yml
View file

@ -15,7 +15,8 @@ services:
environment:
- NODE_ENV=${NODE_ENV:-development}
- APP_PORT=3100
- DATABASE_URL=postgresql://${DB_USER:-insight}:${DB_PASSWORD}@pgbouncer:5432/${DB_NAME:-platform_core}?schema=app_crm
# PgBouncer (transaction mode) strips search_path, so CRM uses direct postgres for queries
- DATABASE_URL=postgresql://${DB_USER:-insight}:${DB_PASSWORD}@postgres:5432/${DB_NAME:-platform_core}?schema=app_crm
- DATABASE_URL_DIRECT=postgresql://${DB_USER:-insight}:${DB_PASSWORD}@postgres:5432/${DB_NAME:-platform_core}?schema=app_crm
- REDIS_HOST=redis
- REDIS_PORT=6379