Skip to content

chore(docker): upgrade to postgresql v18#456

Merged
JeanMeijer merged 2 commits intomainfrom
tembo/upgrade-postgresql-15-to-18-docker-compose
Mar 25, 2026
Merged

chore(docker): upgrade to postgresql v18#456
JeanMeijer merged 2 commits intomainfrom
tembo/upgrade-postgresql-15-to-18-docker-compose

Conversation

@tembo
Copy link
Copy Markdown
Contributor

@tembo tembo bot commented Mar 25, 2026

Description

Upgraded PostgreSQL from version 15 to 18 in Docker Compose and verified configuration compatibility. Updated environment variables and volume paths to match Bitnami PostgreSQL 18 specifications.

Changes Made:

  • Updated docker-compose.yml image from bitnami/postgresql:15 to bitnami/postgresql:18
  • Migrated environment variables to PostgreSQL 18 format:
    • POSTGRES_USER → removed (defaults to postgres)
    • POSTGRES_PASSWORDPOSTGRESQL_POSTGRES_PASSWORD
    • POSTGRES_DBPOSTGRESQL_DATABASE
  • Updated volume mount path from /var/lib/postgresql/data to /bitnami/postgresql
  • Updated healthcheck command to use new environment variable format
  • Added migration guidance in README.md for users upgrading existing local setups

Screenshots / Recordings

N/A

Type of Change

  • Bug fix
  • New feature
  • Breaking change
  • UI/UX update
  • Docs update
  • Refactor / Cleanup

Related Areas

  • Authentication
  • Calendar UI
  • Data/API
  • Docs

Testing

  • Manual testing performed
  • Cross-browser testing (if UI changes)
  • Mobile responsiveness verified (if UI changes)

Checklist

  • I've read the CONTRIBUTING guide
  • My code works and is understandable and follows the project's style guidelines
  • I have performed a self-review of my code
  • I have commented my code, particularly in complex areas
  • I have updated the documentation
  • Any dependent changes are merged and published

Notes

Users with existing PostgreSQL 15 local setups should either run bun run docker:clean to recreate the volume or use PostgreSQL's upgrade tooling before starting the new container.

By submitting, I confirm I understand and stand behind this code. If AI was used, I've reviewed and verified everything myself.


Want tembo to make any changes? Add a review or comment with @tembo and i'll get back to work!

View on Tembo View Agent Settings


Summary by cubic

Upgraded Docker Compose database from PostgreSQL 15 to 18 using bitnami/postgresql:18. Updated env vars, volume path to /bitnami/postgresql, and healthcheck; removed the README upgrade note.

Written for commit 2d078cf. Summary will update on new commits.

…docker-compose and README

Co-authored-by: Jean <9619050+JeanMeijer@users.noreply.github.com>
@vercel
Copy link
Copy Markdown

vercel bot commented Mar 25, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
analog Ready Ready Preview, Comment Mar 25, 2026 1:13am

@tembo tembo bot added the tembo Pull request created by Tembo label Mar 25, 2026
@tembo tembo bot requested a review from JeanMeijer March 25, 2026 01:09
@tembo
Copy link
Copy Markdown
Contributor Author

tembo bot commented Mar 25, 2026

Requesting review from @JeanMeijer who has experience with the following files modified in this PR:

  • README.md

Copy link
Copy Markdown
Contributor

@cubic-dev-ai cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 2 files

Co-authored-by: Jean <9619050+JeanMeijer@users.noreply.github.com>
@JeanMeijer JeanMeijer changed the title Upgrade PostgreSQL 15 to 18 chore(docker): upgrade to postgresql v18 Mar 25, 2026
@JeanMeijer JeanMeijer merged commit f81fc77 into main Mar 25, 2026
7 checks passed
@JeanMeijer JeanMeijer deleted the tembo/upgrade-postgresql-15-to-18-docker-compose branch March 25, 2026 12:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

tembo Pull request created by Tembo

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant