recipe-maintainers/discourse
0
0
Fork 0
Code Issues Pull Requests 4 Actions Packages Projects Releases Wiki Activity

Compare commits

base: recipe-maintainers:discourse-official-image
Branches Tags
recipe-maintainers:main recipe-maintainers:upgrade-c10c04c recipe-maintainers:fix-redis-host recipe-maintainers:discourse-official recipe-maintainers:discourse-official-image recipe-maintainers:fix-pg-migration-idempotent recipe-maintainers:ci/bitnamilegacy-repin recipe-maintainers:renovate/configure recipe-maintainers:cas_readme
recipe-maintainers:1.0.0+3.5.3 recipe-maintainers:0.8.1+3.5.0 recipe-maintainers:0.8.0+3.5.0 recipe-maintainers:0.7.0+3.3.1 recipe-maintainers:0.6.3+3.1.2 recipe-maintainers:0.6.2+3.1.1 recipe-maintainers:0.6.1+3.1.1 recipe-maintainers:0.6.0+3.1.1 recipe-maintainers:0.5.0+3.0.6 recipe-maintainers:0.4.1+3.0.6 recipe-maintainers:0.4.0+3.0.1 recipe-maintainers:0.3.1+2.8.9 recipe-maintainers:0.3.0+2.8.9 recipe-maintainers:0.2.1+2.8.9 recipe-maintainers:0.2.0+2.8.1 recipe-maintainers:0.1.0+2.7.7
..
compare: recipe-maintainers:1.0.0+3.5.3
Branches Tags
recipe-maintainers:upgrade-c10c04c recipe-maintainers:main recipe-maintainers:fix-redis-host recipe-maintainers:discourse-official recipe-maintainers:discourse-official-image recipe-maintainers:fix-pg-migration-idempotent recipe-maintainers:ci/bitnamilegacy-repin recipe-maintainers:renovate/configure recipe-maintainers:cas_readme
recipe-maintainers:1.0.0+3.5.3 recipe-maintainers:0.8.1+3.5.0 recipe-maintainers:0.8.0+3.5.0 recipe-maintainers:0.7.0+3.3.1 recipe-maintainers:0.6.3+3.1.2 recipe-maintainers:0.6.2+3.1.1 recipe-maintainers:0.6.1+3.1.1 recipe-maintainers:0.6.0+3.1.1 recipe-maintainers:0.5.0+3.0.6 recipe-maintainers:0.4.1+3.0.6 recipe-maintainers:0.4.0+3.0.1 recipe-maintainers:0.3.1+2.8.9 recipe-maintainers:0.3.0+2.8.9 recipe-maintainers:0.2.1+2.8.9 recipe-maintainers:0.2.0+2.8.1 recipe-maintainers:0.1.0+2.7.7

3 Commits
discourse- ... 1.0.0+3.5.

Author SHA1 Message Date
notplants
9d5c8ae3ca Merge pull request 'switch app to official discourse/discourse image (with idempotent migration)' (#16) from discourse-official into main 
Reviewed-on: https://git.coopcloud.tech/coop-cloud/discourse/pulls/16
 2026-07-07 22:17:09 +00:00
notplants
1096c38e34 Update release/next 2026-07-07 22:10:56 +00:00
notplants
1f77af93bd feat(db): switch to discourse/postgres image (auto-upgrade)
Some checks failed
cc-ci/testme cc-ci: failure
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
1 changed files with 13 additions and 1 deletions
Expand all files Collapse all files

14
release/1.0.0+3.5.3 → release/next
View File

@ -2,6 +2,8 @@ This release switches from the bitnami image to the official discourse/discourse
image. Some env vars need to be renamed for this migration; everything else image. Some env vars need to be renamed for this migration; everything else
should happen automatically. should happen automatically.
** WARNING A: renaming env vars
Rename these in your app's .env (the values carry over): Rename these in your app's .env (the values carry over):
DISCOURSE_SMTP_HOST --> DISCOURSE_SMTP_ADDRESS DISCOURSE_SMTP_HOST --> DISCOURSE_SMTP_ADDRESS
@ -9,7 +11,17 @@ Rename these in your app's .env (the values carry over):
DISCOURSE_SMTP_AUTH --> DISCOURSE_SMTP_AUTHENTICATION DISCOURSE_SMTP_AUTH --> DISCOURSE_SMTP_AUTHENTICATION
DISCOURSE_SMTP_PROTOCOL --> DISCOURSE_SMTP_ENABLE_START_TLS (takes a boolean true/false, not the old tls/ssl value, so translate it rather than copying it straight across) DISCOURSE_SMTP_PROTOCOL --> DISCOURSE_SMTP_ENABLE_START_TLS (takes a boolean true/false, not the old tls/ssl value, so translate it rather than copying it straight across)
WARNING: if your deployment's database has an "install user" other than `postgres` ** WARNING B: undeploy before deploy
it is necessary to `abra app undeploy` your old discourse app before deploying this version. otherwise the database will get killed and be in a bad state before the migration.
this was a non-fatal error in testing, but still a huge pain.
`abra app undeploy YOURDOMAIN` # cleaning stops your discourse
`abra app deploy YOURDOMAIN` # with the new version
** WARNING C: install user
if your deployment's database has an "install user" other than `postgres`
(some older deployments do), you must set the POSTGRES_USER env var in your .env (some older deployments do), you must set the POSTGRES_USER env var in your .env
for this migration, otherwise the postgres upgrade aborts with an install-user for this migration, otherwise the postgres upgrade aborts with an install-user
mismatch. mismatch.