Fixes the Discourse template which was broken due to Bitnami discontinuing their legacy images (bitnami/discourse, bitnami/postgresql, bitnami/redis, bitnamilegacy).
Changes:
Replaced bitnamilegacy/discourse:3.5.0 with discourse/discourse:2026.1.4 (official ESR image)
Replaced bitnami/postgresql:17 with pgvector/pgvector:pg16 (required for Discourse's vector extension)
Replaced bitnami/redis:7.4 with redis:7-alpine
Removed separate sidekiq container — the official image runs web + sidekiq internally via runit
Updated all env var names from Bitnami-specific (DISCOURSE_DATABASE_*, POSTGRESQL_*) to standard ones (DISCOURSE_DB_*, POSTGRES_*)
Added UNICORN_BIND_ALL: "true" to allow the proxy to reach the web process
Added DISCOURSE_DEVELOPER_EMAILS variable to template.toml so admin email is set at deploy time
I have tested the template in my instance, so the maintainers don't spend time trying to figure out what's wrong.
I have added tests that demonstrate that my correction works or that my new feature works.
Issues related (if applicable)
Closed: #502 - Fix was replacing with BitnamiLegacy images which may soon be deprecated. Replacing with official images ensures that Bitnami does not have control to pull the plug suddenly again.
Screenshots or Videos
Note: The "Tada" SVG is not showing due to it not being served on HTTPS/SSL. This is using sslip for testing. SMTP is partially required for Discourse otherwise manual admin account creation is required, and it disables a lot of features that require emails. Refer to this
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/Dokploy/templates/pull/910
**Author:** [@MagiqueDeveloper](https://github.com/MagiqueDeveloper)
**Created:** 5/26/2026
**Status:** 🔄 Open
**Base:** `canary` ← **Head:** `canary`
---
### 📝 Commits (4)
- [`d23274d`](https://github.com/Dokploy/templates/commit/d23274d7d474c225aed0f8e99426d24f3484675b) refactor(docker-compose): update PostgreSQL and Redis images, adjust environment variables
- [`a80d048`](https://github.com/Dokploy/templates/commit/a80d048e7525608493afb501e58e5d586f992212) chore(meta.json): update Discourse version to 2026.1.4
- [`dbc2e43`](https://github.com/Dokploy/templates/commit/dbc2e4342628a259f2f233bdf31a671d65b2a595) chore(docker-compose): comment out DISCOURSE_FORCE_HTTPS for production
- [`d112470`](https://github.com/Dokploy/templates/commit/d112470138274e3b4b89c00117ecf1fa0e00e739) fix(docker-compose): update Discourse app port to 80 for production
### 📊 Changes
**3 files changed** (+32 additions, -56 deletions)
<details>
<summary>View changed files</summary>
📝 `blueprints/discourse/docker-compose.yml` (+27 -53)
📝 `blueprints/discourse/template.toml` (+4 -2)
📝 `meta.json` (+1 -1)
</details>
### 📄 Description
## What is this PR about?
Fixes the Discourse template which was broken due to Bitnami discontinuing their legacy images (`bitnami/discourse`, `bitnami/postgresql`, `bitnami/redis`, `bitnamilegacy`).
**Changes:**
- Replaced `bitnamilegacy/discourse:3.5.0` with `discourse/discourse:2026.1.4` (official ESR image)
- Replaced `bitnami/postgresql:17` with `pgvector/pgvector:pg16` (required for Discourse's vector extension)
- Replaced `bitnami/redis:7.4` with `redis:7-alpine`
- Removed separate sidekiq container — the official image runs web + sidekiq internally via runit
- Updated all env var names from Bitnami-specific (`DISCOURSE_DATABASE_*`, `POSTGRESQL_*`) to standard ones (`DISCOURSE_DB_*`, `POSTGRES_*`)
- Added `UNICORN_BIND_ALL: "true"` to allow the proxy to reach the web process
- Added `DISCOURSE_DEVELOPER_EMAILS` variable to `template.toml` so admin email is set at deploy time
- Consolidated volumes from 4 down to 3
## Checklist
Before submitting this PR, please make sure that:
- [x] I have read the suggestions in the README.md file https://github.com/Dokploy/templates?tab=readme-ov-file#general-requirements-when-creating-a-template
- [x] I have tested the template in my instance, so the maintainers don't spend time trying to figure out what's wrong.
- [ ] I have added tests that demonstrate that my correction works or that my new feature works.
## Issues related (if applicable)
Closed: #502 - Fix was replacing with BitnamiLegacy images which may soon be deprecated. Replacing with official images ensures that Bitnami does not have control to pull the plug suddenly again.
## Screenshots or Videos
<img width="1278" height="686" alt="Discourse Setup Wizard" src="https://github.com/user-attachments/assets/9eec0bae-7d81-4b0a-9720-526a088d88a1" />
<img width="2482" height="1386" alt="Disource App Logs" src="https://github.com/user-attachments/assets/ed56940a-0228-4536-8646-b52fa37bd714" />
<img width="2482" height="1386" alt="Discourse Redis Logs" src="https://github.com/user-attachments/assets/e631eb24-984a-416a-b6ae-65fe2ef06dd9" />
<img width="2482" height="1386" alt="Discourse DB Logs" src="https://github.com/user-attachments/assets/16f05ba4-631b-43ab-aafa-2912c00b56d5" />
~~Note: The "Tada" SVG is not showing due to it not being served on HTTPS/SSL. This is using **sslip** for testing. SMTP is partially required for Discourse otherwise manual admin account creation is required, and it disables a lot of features that require emails.~~ Refer to [this](https://github.com/Dokploy/templates/pull/910#issuecomment-4550408174)
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/Dokploy/templates/pull/910
Author: @MagiqueDeveloper
Created: 5/26/2026
Status: 🔄 Open
Base:
canary← Head:canary📝 Commits (4)
d23274drefactor(docker-compose): update PostgreSQL and Redis images, adjust environment variablesa80d048chore(meta.json): update Discourse version to 2026.1.4dbc2e43chore(docker-compose): comment out DISCOURSE_FORCE_HTTPS for productiond112470fix(docker-compose): update Discourse app port to 80 for production📊 Changes
3 files changed (+32 additions, -56 deletions)
View changed files
📝
blueprints/discourse/docker-compose.yml(+27 -53)📝
blueprints/discourse/template.toml(+4 -2)📝
meta.json(+1 -1)📄 Description
What is this PR about?
Fixes the Discourse template which was broken due to Bitnami discontinuing their legacy images (
bitnami/discourse,bitnami/postgresql,bitnami/redis,bitnamilegacy).Changes:
bitnamilegacy/discourse:3.5.0withdiscourse/discourse:2026.1.4(official ESR image)bitnami/postgresql:17withpgvector/pgvector:pg16(required for Discourse's vector extension)bitnami/redis:7.4withredis:7-alpineDISCOURSE_DATABASE_*,POSTGRESQL_*) to standard ones (DISCOURSE_DB_*,POSTGRES_*)UNICORN_BIND_ALL: "true"to allow the proxy to reach the web processDISCOURSE_DEVELOPER_EMAILSvariable totemplate.tomlso admin email is set at deploy timeChecklist
Before submitting this PR, please make sure that:
Issues related (if applicable)
Closed: #502 - Fix was replacing with BitnamiLegacy images which may soon be deprecated. Replacing with official images ensures that Bitnami does not have control to pull the plug suddenly again.
Screenshots or Videos
Note: The "Tada" SVG is not showing due to it not being served on HTTPS/SSL. This is using sslip for testing. SMTP is partially required for Discourse otherwise manual admin account creation is required, and it disables a lot of features that require emails.Refer to this🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.