coop-cloud/discourse
0
0
Fork 2
Code Issues 10 Pull Requests 1 Projects Releases Wiki Activity

switch app to official discourse/discourse image (with idempotent migration) #16

Merged
notplants merged 3 commits from discourse-official into main 2026-07-07 22:17:09 +00:00
Conversation 4 Commits 3 Files Changed 11
+254 -208
3 Commits
Author SHA1 Message Date
notplants 1096c38e34 Update release/next
continuous-integration/drone/pr Build is failing
Details
2026-07-07 22:10:56 +00:00
notplants 1f77af93bd feat(db): switch to discourse/postgres image (auto-upgrade)
continuous-integration/drone/pr Build is failing
Details 
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.
 2026-06-22 19:57:54 +00:00
notplants 0c4539b7ad feat(discourse): switch app to official discourse/discourse image (experimental)
continuous-integration/drone/pr Build is failing
Details 
Replaces the paywalled bitnamilegacy app with the official discourse/discourse
image behind Traefik. DB is reused as-is; uploads migrate from the legacy
bitnami volume idempotently. The wrapper entrypoint injects the db_password and
smtp_password secrets (the official image has no *_FILE support). SMTP env vars
are renamed to the official names; release notes cover the migration.

Recipe 0.8.1+3.5.0 -> 1.0.0+3.5.3 (major: new image, env/volume/port changes).
 2026-06-18 21:59:34 +00:00