Files

notplants 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

2.9 KiB

Raw Blame History

Discourse

A platform for community discussion

Category: Apps
Status: 3, experimental
Image: discourse/discourse, 4, upstream
Healthcheck: yes
Backups: yes
Email: yes
Tests: yes
SSO: no

Note

: this recipe runs the official, experimental discourse/discourse image. Upstream does not yet recommend it for production — see https://meta.discourse.org/t/380646. Use with care.

Basic usage

Set up Docker Swarm and abra
Deploy coop-cloud/traefik
abra app new discourse --secrets
abra app config YOURAPPDOMAIN — set DOMAIN and DISCOURSE_DEVELOPER_EMAILS
abra app deploy YOURAPPDOMAIN
Open the configured domain in your browser to finish set-up. The first account that registers with an address listed in DISCOURSE_DEVELOPER_EMAILS becomes an admin.

The app serves plain HTTP on port 80; Traefik terminates TLS in front of it. The image's built-in nginx/Let's Encrypt is disabled by the recipe (install-ssl override) so it works behind the reverse proxy.

Add an admin user

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.

Migrating from the previous (bitnami) recipe

The official image stores uploads under /shared rather than bitnami's /bitnami/discourse. On first boot the recipe copies uploads + backups from the old bitnami volume (mounted read-only at /legacy) into /shared, once, idempotently. The Postgres database is reused as-is. After a successful migration a later recipe version will drop the transitional /legacy mount.

If you are upgrading from the bitnami recipe, also remove the now-unused sidekiq service that swarm leaves behind (sidekiq runs inside the app container now):

docker service rm YOURSTACK_sidekiq