notplants
af76d06c2d
discourse core does not use the vector extension, so the pgvector image is unnecessary. Switch db to pgautoupgrade/pgautoupgrade:17-trixie, which handles major-version upgrades (old binaries, initdb, pg_upgrade) itself. pgautoupgrade assumes the old cluster's install user (oid 10) equals POSTGRES_USER and fails pg_upgrade otherwise (issue #115). A thin wrapper entrypoint detects the old install user when an upgrade is pending and exports POSTGRES_USER so pgautoupgrade matches it. Replaces the 64-line hand-rolled pg_upgrade entrypoint.
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/discourseimage. 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 --secretsabra app config YOURAPPDOMAIN— setDOMAINandDISCOURSE_DEVELOPER_EMAILSabra 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_EMAILSbecomes 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
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