8 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
notplantsandnotplants	a5a3b36755	feat(db): use POSTGRES_USER in pg_backup; document it in release note ... - pg_backup.sh: use the db service's POSTGRES_USER (default postgres) for the dump/drop/recreate instead of detecting the superuser at runtime, since the recipe now sets that env var; one-line the constants comment - release note: explain the in-place pg_upgrade + the POSTGRES_USER override - bump PG_BACKUP_VERSION v4 Verified on cctest: backup + restore via the hooks round-trips with POSTGRES_USER.	2026-06-22 18:46:17 +00:00
notplantsandnotplants	f783d9988b	feat(db): switch to discourse/postgres image (auto-upgrade, no custom entrypoint file) ... Replace the bitnami-era pgvector:pg17 db + hand-rolled pg_upgrade entrypoint with discourse/postgres:pg18 (pgvector + discourse's auto-upgrade layer, as suggested on coop-cloud/discourse#16). The image runs the in-place major-version pg_upgrade itself on boot, so the recipe just configures it via env: - the db password secret is read into $DB_PASSWORD by a small inline entrypoint (the image expects it in the env, no *_FILE support; the base image's POSTGRES_PASSWORD_FILE can't be used because run-postgres.sh pre-generates POSTGRES_PASSWORD). No separate entrypoint file/config any more. - POSTGRES_USER (the install user pg_upgrade must match) defaults to the image's 'postgres' -- correct for fresh installs and bitnami-origin clusters -- and is overridable from the app .env for a cluster bootstrapped with another superuser. - POSTGRES_INITDB_ARGS=--no-data-checksums so the new pg18 cluster matches the pre-18 clusters (pg18 initdb enables checksums by default; pg_upgrade needs a match). - mount postgresql_data at /var/lib/postgresql (versioned PGDATA .../18/docker) - pg_backup.sh: detect the superuser at runtime; fix paths for the new layout - document POSTGRES_USER override in .env.sample and README - bump PG_BACKUP_VERSION v3; drop DB_ENTRYPOINT_VERSION + entrypoint.postgres.sh.tmpl Verified on cctest: pg17->pg18 upgrade (install user 'postgres', checksums off) preserves data and serves over HTTPS; fresh install also works.	2026-06-22 18:23:22 +00:00
notplants	f87c612d71	chore: publish 0.8.1+3.5.0 release	2026-06-16 14:46:48 -04:00
notplantsandnotplants	a9f08eed28	fix(db): make pg_upgrade 13->17 idempotent and use the cluster's real install user	2026-06-16 18:29:24 +00:00
notplantsandnotplants	b0f9ae743a	fix(db): switch postgres image to pgvector/pgvector:pg17 + bump PG_BACKUP_VERSION	2026-06-02 20:07:06 +00:00
notplantsandnotplants	5091fd999e	improved comments	2026-06-02 19:10:27 +00:00
notplantsandnotplants	ec7bbdf786	fix(backup): add pg_backup.sh + proper backup/restore hooks, 20m start_period	2026-06-02 19:10:27 +00:00
notplantsandnotplants	0f873433ba	chore: upgrade to 0.8.0+3.5.0	2026-06-02 19:10:27 +00:00