Modify PG_DATABASE_URL to include PG_DATABASE_NAME - #24091
Conversation
Updated PG_DATABASE_URL to use PG_DATABASE_NAME variable.
|
👋 Thanks for contributing to Twenty! We're excited to have you on board. Your PR has been set to draft while you work on it. Once you're done, mark it as Ready for review and our automated checks will run. By submitting your Pull Request, you acknowledge that you agree with the terms of our Contributor License Agreement. |
There was a problem hiding this comment.
Pull request overview
Updates the Docker Compose configuration for the Twenty stack so the Postgres connection string (PG_DATABASE_URL) derives its database name from PG_DATABASE_NAME, aligning runtime connectivity with the database container’s POSTGRES_DB setting.
Changes:
- Use
${PG_DATABASE_NAME:-default}as the database path segment inPG_DATABASE_URLfor theserverservice. - Use
${PG_DATABASE_NAME:-default}as the database path segment inPG_DATABASE_URLfor theworkerservice.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Greptile SummaryThe PR makes the Docker Compose server and worker database URLs honor
Confidence Score: 5/5The PR appears safe to merge with no actionable issues identified. The server, worker, and Postgres service resolve the same database name, while the existing default behavior remains unchanged when the variable is unset. Important Files Changed
Reviews (1): Last reviewed commit: "Modify PG_DATABASE_URL to include PG_DAT..." | Re-trigger Greptile |
Welcome!
Hello there, congrats on your first PR! We're excited to have you contributing to this project. |
Updated PG_DATABASE_URL to use PG_DATABASE_NAME variable.