f783d9988b
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.
5 lines
133 B
Bash
5 lines
133 B
Bash
export PG_BACKUP_VERSION=v3
|
|
export APP_ENTRYPOINT_VERSION=v2
|
|
export APP_INSTALL_SSL_VERSION=v1
|
|
export APP_MIGRATE_UPLOADS_VERSION=v1
|