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

fix(image): re-pin bitnami->bitnamilegacy/discourse:3.3.1 (Docker Hub emptied bitnami/discourse) #1

Closed
autonomic-bot wants to merge 3 commits from ci/bitnamilegacy-repin into main
pull from: ci/bitnamilegacy-repin
merge into: :main
Conversation 2 Commits 3 Files Changed 4
+67 -7
autonomic-bot commented 2026-05-30 09:52:37 +00:00
Owner
Copy Link
Copy Source

bitnami/discourse:3.3.1 is unservable (Docker Hub emptied the namespace; manifest 404). bitnamilegacy/discourse:3.3.1 is the byte-identical archived drop-in (manifest 200, confirmed first-hand). Re-pins both app + sidekiq services. Found via cc-ci enrollment.

bitnami/discourse:3.3.1 is unservable (Docker Hub emptied the namespace; manifest 404). bitnamilegacy/discourse:3.3.1 is the byte-identical archived drop-in (manifest 200, confirmed first-hand). Re-pins both app + sidekiq services. Found via cc-ci enrollment.
autonomic-bot added 1 commit 2026-05-30 09:52:37 +00:00
fix(image): re-pin bitnami/discourse -> bitnamilegacy/discourse:3.3.1 7b7ddd70bc 
Docker Hub emptied the bitnami/discourse namespace (manifest 3.3.1 -> 404, tags:[]); Bitnami moved
archived images to the bitnamilegacy namespace. bitnamilegacy/discourse:3.3.1 is the byte-identical
drop-in (manifest -> 200, same /bitnami/discourse paths + /opt/bitnami scripts). Re-pin both app +
sidekiq services; bump 0.7.0 -> 0.8.0. Found via cc-ci enrollment.
autonomic-bot added 1 commit 2026-05-30 14:03:47 +00:00
fix(backup): reimport postgres dump on restore (restore was a no-op) 2fd5e37f55 
The db service dumped the DB on backup (pg_dump pre-hook) but shipped no
restore hook, and a file-level restore does not reload into the running
postgres, so a restored backup silently kept the live (un-restored) state.
Add pg_backup.sh (backup=pg_dump|gzip into the postgresql_data volume;
restore=terminate conns + DROP DATABASE WITH FORCE + createdb + reimport),
mount it via a config, and wire the backupbot backup/restore hooks. Same
fix as the immich / mattermost-lts / ghost recipes.
autonomic-bot force-pushed ci/bitnamilegacy-repin from 2fd5e37f55 to 04bb9db7b6 2026-05-30 14:07:00 +00:00 Compare
autonomic-bot force-pushed ci/bitnamilegacy-repin from 04bb9db7b6 to 0926a42d2e 2026-05-30 14:13:11 +00:00 Compare
autonomic-bot force-pushed ci/bitnamilegacy-repin from 0926a42d2e to c8ba2e4e2b 2026-05-30 14:45:23 +00:00 Compare
autonomic-bot force-pushed ci/bitnamilegacy-repin from c8ba2e4e2b to 70891e2fb5 2026-05-30 15:09:09 +00:00 Compare
autonomic-bot force-pushed ci/bitnamilegacy-repin from 70891e2fb5 to 7a2e0e044c 2026-05-30 15:19:28 +00:00 Compare
autonomic-bot added 1 commit 2026-05-30 23:37:33 +00:00
fix(backup): block reconnections via pg_hba during pg restore (app reconnect broke reimport) 3758522cf8
autonomic-bot commented 2026-06-02 00:07:51 +00:00
Author
Owner
Copy Link
Copy Source

@notplants — flagging this open PR from the cc-ci build for your review. Per the updated mirror workflow we no longer auto-close superseded/unrelated PRs, so it's left open for you to merge or close at your discretion.

@notplants — flagging this open PR from the cc-ci build for your review. Per the updated mirror workflow we no longer auto-close superseded/unrelated PRs, so it's left open for you to merge or close at your discretion.
autonomic-bot commented 2026-08-10 20:25:02 +00:00
Author
Owner
Copy Link
Copy Source

Closing as obsolete: re-pins the app back to bitnamilegacy/discourse:3.3.1 and the version label to 0.8.0+3.3.1, and restores the old ruby healthcheck. upstream main is now discourse/discourse:3.5.3 + discourse/postgres:pg18 (version 1.0.0+3.5.3, commit 9d5c8ae) — the official-image migration landed upstream as coop-cloud/discourse#16. Merging this would REVERT the migration, so it is obsolete.

The live upgrade PR for discourse is #6 (discourse/discourse:3.5.3 → 2026.7.1, redis:7.4-alpine → 8.10-alpine), which applies cleanly on top of current upstream and stays open.

Closing as **obsolete**: re-pins the app back to `bitnamilegacy/discourse:3.3.1` and the version label to `0.8.0+3.3.1`, and restores the old ruby healthcheck. upstream main is now `discourse/discourse:3.5.3` + `discourse/postgres:pg18` (version `1.0.0+3.5.3`, commit 9d5c8ae) — the official-image migration landed upstream as coop-cloud/discourse#16. Merging this would REVERT the migration, so it is obsolete. The live upgrade PR for discourse is #6 (`discourse/discourse:3.5.3 → 2026.7.1`, `redis:7.4-alpine → 8.10-alpine`), which applies cleanly on top of current upstream and stays open.
autonomic-bot closed this pull request 2026-08-10 20:25:02 +00:00

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
autonomic autonomic-bot kawaiipunk (KawaiiPunk) notplants trav (Trav Fryer)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: recipe-maintainers/discourse#1