feat(discourse): switch app to official discourse/discourse image (experimental)

Replaces the paywalled bitnamilegacy app with the official discourse/discourse
image behind Traefik (HTTP-only via an install-ssl override; sidekiq is internal
so its service is dropped). DB is reused as-is; uploads migrate from a legacy
bitnami volume via an idempotent, non-destructive runit hook. db keeps
pgvector/pgvector:pg17 with the install-user-aware pg_upgrade entrypoint, plus
db/redis healthchecks and updated README metadata (lint R002/R007).

Verified on cctest: fresh install, upgrade-from-bitnami-pg17, and
upgrade-from-bitnami-pg13 (incl. 13->17) all serve with data intact.
Upstream marks discourse/discourse experimental; hold prod cutover.

Recipe 0.8.1+3.5.0 -> 1.0.0+3.5.3 (major: new image, env/volume/port changes).

README.md

@@ -6,67 +6,60 @@ A platform for community discussion
 
 <!-- metadata -->
 * **Category**: Apps
-* **Status**: 
+* **Status**: 3, experimental
-* **Image**: [`bitnami/discourse`](https://hub.docker.com/r/bitnami/discourse)
+* **Image**: [`discourse/discourse`](https://hub.docker.com/r/discourse/discourse), 4, upstream
 * **Healthcheck**: yes
-* **Backups**: no
+* **Backups**: yes
 * **Email**: yes
-* **Tests**: no
+* **Tests**: yes
 * **SSO**: no
 <!-- endmetadata -->
 
+> **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
 
 1. Set up Docker Swarm and [`abra`]
 2. Deploy [`coop-cloud/traefik`]
-3. `abra app new discourse --secrets` (optionally with `--pass` if you'd like
+3. `abra app new discourse --secrets` (optionally with `--pass` to save secrets in `pass`)
-   to save secrets in `pass`)
+4. `abra app config YOURAPPDOMAIN` — set `DOMAIN` and `DISCOURSE_DEVELOPER_EMAILS`
-4. `abra app config YOURAPPDOMAIN` - be sure to change `$DOMAIN` to something that resolves to
-   your Docker swarm box
 5. `abra app deploy YOURAPPDOMAIN`
-6. Open the configured domain in your browser to finish set-up
+6. 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.
 
-[`abra`]: https://git.autonomic.zone/autonomic-cooperative/abra
+[`abra`]: https://docs.coopcloud.tech/abra/
-[`coop-cloud/traefik`]: https://git.autonomic.zone/coop-cloud/traefik
+[`coop-cloud/traefik`]: https://git.coopcloud.tech/coop-cloud/traefik
 
-## To add a new admin user
+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.
 
-1. Login to the instance `abra app run APPNAME app sh`
+## Add an admin user
-2. `cd /opt/bitnami/discourse`
-3. `RAILS_ENV=production bundle exec rake admin:create` and follow prompts.
 
-## Install plugins
+```
-
+abra app run YOURAPPDOMAIN app discourse admin create
-1. Login to instance `abra app run APPNAME app sh`
+```
-2. `cd /bitnami/discourse/plugins/`
-3. `git clone plugin.git` for example `https://github.com/discourse/discourse-openid-connect.git`
-4. `abra app restart YOURAPPDOMAIN app`
-
-### Events / calendar plugin
-
-We've had some luck running [discourse-events](https://github.com/paviliondev/discourse-events).
-
-## Setup Notes
-
-Until issue #1 is fixed, the default user is `user` and the default password is `bitnami123`
 
 ## Postgres major version upgrades
 
-Welcome to hell.
+Handled automatically. The `db` entrypoint detects an older data directory on
+deploy and runs `pg_upgrade` in place (it installs the old binaries, detects the
+cluster's real install superuser, and upgrades). No manual dump/restore needed.
 
-1. `abra app run YOURAPPDOMAIN db pg_dumpall -U discourse | gzip > YOURAPPDOMAIN_db_DATE.sql.gz`
+## Migrating from the previous (bitnami) recipe
-2. `abra app volume ls YOURAPPDOMAIN`, find the name of the Postgres data volume
+
-3. `scp` the backup to your VPS
+The official image stores uploads under `/shared` rather than bitnami's
-4. `abra app undeploy YOURAPPDOMAIN`
+`/bitnami/discourse`. On first boot the recipe copies uploads + backups from the
-5. `abra app volume rm YOURAPPDOMAIN`, choose the Postgres data volume
+old bitnami volume (mounted read-only at `/legacy`) into `/shared`, once,
-6. `abra app deploy YOURAPPDOMAIN`, then `abra app undeploy YOURAPPDOMAIN`
+idempotently. The Postgres database is reused as-is. After a successful migration
-7. `ssh` to the VPS, run (replacing `13-alpine` with the new Postgres version)
+a later recipe version will drop the transitional `/legacy` mount.
-   `docker run -v YOURDATAVOLUME:/var/lib/postgresql/data -e POSTGRES_HOST_AUTH_METHOD=trust -it postgres:13-alpine`
+
-8. In another SSH session on the server, run `docker ps` to find the ID of the
+If you are upgrading from the bitnami recipe, also remove the now-unused sidekiq
-   new Postgres container, then `docker exec -it CONTAINERID bash`
+service that swarm leaves behind (sidekiq runs inside the app container now):
-9. In the shell you just launched, run `dropdb -U discourse discourse`, then
+
-   `createdb -U discourse discourse`, then Ctrl+D or run `exit`
+```
-10. In the second SSH session, run `zcat YOURAPPDOMAIN_db_DATE.sql.gz | docker exec -it CONTAINERID psql -U discourse`
+docker service rm YOURSTACK_sidekiq
-11. Exit the second SSH session
+```
-12. Back in the first SSH session, Ctrl+C to shut down the database
-13. `abra app deploy YOURAPPDOMAIN`

compose.yml

@@ -83,6 +83,15 @@ services:
       - POSTGRES_USER=discourse
       - POSTGRES_DB=discourse
       - POSTGRES_PASSWORD_FILE=/run/secrets/db_password
+    healthcheck:
+      test: "pg_isready -U discourse -d discourse"
+      interval: 30s
+      timeout: 10s
+      retries: 5
+      # generous: a postgres major-version upgrade (apt install + pg_upgrade) runs
+      # in the entrypoint before the server accepts connections — don't let the
+      # healthcheck kill an in-progress migration
+      start_period: 10m
     deploy:
       labels:
         backupbot.backup: "true"
@@ -96,6 +105,12 @@ services:
       - internal
     volumes:
       - 'redis_data:/data'
+    healthcheck:
+      test: "redis-cli ping | grep -q PONG"
+      interval: 30s
+      timeout: 5s
+      retries: 5
+      start_period: 30s
 
 secrets:
   db_password: