twenty/packages/twenty-docker
azaurus1 bb5cc7e30c
Update PG_DATABASE_URL to match Service name in k8s manifests (#8989)
### Issue Summary
The `service` name in the Kubernetes manifest for the PostgreSQL
database is defined as `twentycrm-db`. However, the `DSN` configuration
in the Server and Worker `deployments` incorrectly references
`twenty-db`. This mismatch causes the pods to fail during initialization
and crash on boot.

### Fix Description
- Updated the `DSN` values in both the Server and Worker `deployments`
to correctly reference `twentycrm-db`, ensuring alignment with the
database `service` name.
- Verified the deployments to ensure the pods start without issues after
the fix.

### Testing
- Deployed the updated manifests in a development environment.
- Confirmed that both Server and Worker pods initialize correctly and
connect to the database service as expected.
2024-12-10 08:21:38 +01:00
..
k8s Update PG_DATABASE_URL to match Service name in k8s manifests (#8989) 2024-12-10 08:21:38 +01:00
scripts Fix 1-click install tag version (#8709) 2024-11-24 19:08:04 +01:00
twenty Fail entrypoint if migration fails (#8590) 2024-11-19 18:57:15 +01:00
twenty-postgres-spilo Begin moving to postgres spilo + adding pgvector (#8309) 2024-11-15 09:38:30 +01:00
twenty-website Put back twenty-website dockerfile 2024-10-15 18:36:10 +02:00
.env.example Begin moving to postgres spilo + adding pgvector (#8309) 2024-11-15 09:38:30 +01:00
docker-compose.yml Updated website docs and /twenty-server/.env (#8801) 2024-11-29 14:12:09 +01:00
Makefile Begin moving to postgres spilo + adding pgvector (#8309) 2024-11-15 09:38:30 +01:00