feat(db): switch to discourse/postgres image (auto-upgrade)
Some checks failed
cc-ci/testme cc-ci: failure
Some checks failed
cc-ci/testme cc-ci: failure
Move the db off the bitnami-era pgvector:pg17 + hand-rolled pg_upgrade entrypoint to discourse/postgres:pg18 (pgvector + discourse's auto-upgrade layer). The image runs the in-place major-version pg_upgrade itself on boot; the recipe configures it via env: - a small inline entrypoint injects the db password secret into $DB_PASSWORD (the image expects it in the env, no *_FILE support) - POSTGRES_USER (the install user pg_upgrade must match) defaults to 'postgres' -- correct for fresh installs and bitnami-origin clusters -- overridable from .env - POSTGRES_INITDB_ARGS=--no-data-checksums so the new pg18 cluster matches 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 uses POSTGRES_USER for the dump/drop/recreate; fix paths - document the POSTGRES_USER override in .env.sample, README and the release note - drop entrypoint.postgres.sh.tmpl Tested on cctest: pg17->pg18 upgrade preserves data and serves over HTTPS; fresh install works; backup+restore round-trips.
This commit is contained in:
16
README.md
16
README.md
@ -43,6 +43,22 @@ override) so it works behind the reverse proxy.
|
||||
abra app run YOURAPPDOMAIN app discourse admin create
|
||||
```
|
||||
|
||||
## Postgres major version upgrades
|
||||
|
||||
Handled automatically by the [`discourse/postgres`] image (pgvector + an
|
||||
auto-upgrade layer). On deploy it finds an older cluster, installs the old
|
||||
binaries and runs `pg_upgrade` into the new versioned data directory. No manual
|
||||
dump/restore needed.
|
||||
|
||||
`pg_upgrade` must run as the old cluster's bootstrap superuser (its "install
|
||||
user"). The recipe uses `POSTGRES_USER`, which defaults to `postgres` — the right
|
||||
value for fresh installs and for clusters that came from the old bitnami recipe.
|
||||
If your cluster was bootstrapped with a different superuser (e.g. `discourse`),
|
||||
set `POSTGRES_USER` in the app `.env` before upgrading, otherwise `pg_upgrade`
|
||||
will refuse with an install-user mismatch.
|
||||
|
||||
[`discourse/postgres`]: https://github.com/discourse/discourse-postgres
|
||||
|
||||
## Migrating from the previous (bitnami) recipe
|
||||
|
||||
The official image stores uploads under `/shared` rather than bitnami's
|
||||
|
||||
Reference in New Issue
Block a user