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)
Close automatically the related issues using the keywords: closes #ISSUE_NUMBER
Screenshots or Videos
Greptile Summary
This PR adds a new Tuwunel blueprint — a Rust-based Matrix homeserver — with a docker-compose.yml, template.toml, logo.svg, and the corresponding meta.json entry. The overall structure follows repository conventions, the image is pinned to a specific version, and the strapi/streamflow reorder in meta.json is a correct alphabetical fix from running dedupe-and-sort-meta.js.
Issues found:
Registration enabled by default (logic):template.toml hardcodes TUWUNEL_ALLOW_REGISTRATION=true, silently overriding the false default in docker-compose.yml. This means every deployment ships with registration turned on. Even though a random token is generated, it is exposed in the deployment configuration. The safer default is false, letting operators opt-in after deployment.
Logo filename convention (style): The logo is named logo.svg instead of tuwunel.svg. All other blueprints name their logo after the application (e.g., ghost.jpeg, strapi.svg), per the conventions in AGENTS.md.
Confidence Score: 3/5
Safe to merge after resolving the open-registration default and logo naming issue.
The template is well-structured and follows most conventions, but hardcoding TUWUNEL_ALLOW_REGISTRATION=true contradicts the safer false default in the compose file and poses a security concern for a self-hosted Matrix server. The logo naming deviation is minor but should also be fixed before merging.
blueprints/tuwunel/template.toml (registration default) and blueprints/tuwunel/logo.svg / meta.json (logo filename convention).
🔄 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/733
**Author:** [@AdrianBonpin](https://github.com/AdrianBonpin)
**Created:** 3/3/2026
**Status:** ✅ Merged
**Merged:** 3/5/2026
**Merged by:** [@Siumauricio](https://github.com/Siumauricio)
**Base:** `canary` ← **Head:** `tuwunel`
---
### 📝 Commits (3)
- [`fdeef0e`](https://github.com/Dokploy/templates/commit/fdeef0ea0fe26968f37ea783a48c5bf93f4a1345) feat: add tuwunel template for matrix
- [`5f6fa36`](https://github.com/Dokploy/templates/commit/5f6fa36231f1a407a466dc2b688a6960041de721) fix: replace HTML placeholder with actual SVG logo for tuwunel
- [`0b7cef6`](https://github.com/Dokploy/templates/commit/0b7cef6cb8dfd7d38c78761bf3e72036c4deb9c3) fix: remove enforcement and rename logo
### 📊 Changes
**4 files changed** (+73 additions, -18 deletions)
<details>
<summary>View changed files</summary>
➕ `blueprints/tuwunel/docker-compose.yml` (+18 -0)
➕ `blueprints/tuwunel/template.toml` (+15 -0)
➕ `blueprints/tuwunel/tuwunel.svg` (+4 -0)
📝 `meta.json` (+36 -18)
</details>
### 📄 Description
## What is this PR about?
Remake of PR to add tuwunel (matrix backend)
## 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)
Close automatically the related issues using the keywords: `closes #ISSUE_NUMBER`
## Screenshots or Videos
<!-- greptile_comment -->
<h3>Greptile Summary</h3>
This PR adds a new Tuwunel blueprint — a Rust-based Matrix homeserver — with a `docker-compose.yml`, `template.toml`, `logo.svg`, and the corresponding `meta.json` entry. The overall structure follows repository conventions, the image is pinned to a specific version, and the `strapi`/`streamflow` reorder in `meta.json` is a correct alphabetical fix from running `dedupe-and-sort-meta.js`.
**Issues found:**
- **Registration enabled by default (logic):** `template.toml` hardcodes `TUWUNEL_ALLOW_REGISTRATION=true`, silently overriding the `false` default in `docker-compose.yml`. This means every deployment ships with registration turned on. Even though a random token is generated, it is exposed in the deployment configuration. The safer default is `false`, letting operators opt-in after deployment.
- **Logo filename convention (style):** The logo is named `logo.svg` instead of `tuwunel.svg`. All other blueprints name their logo after the application (e.g., `ghost.jpeg`, `strapi.svg`), per the conventions in `AGENTS.md`.
<h3>Confidence Score: 3/5</h3>
- Safe to merge after resolving the open-registration default and logo naming issue.
- The template is well-structured and follows most conventions, but hardcoding `TUWUNEL_ALLOW_REGISTRATION=true` contradicts the safer `false` default in the compose file and poses a security concern for a self-hosted Matrix server. The logo naming deviation is minor but should also be fixed before merging.
- `blueprints/tuwunel/template.toml` (registration default) and `blueprints/tuwunel/logo.svg` / `meta.json` (logo filename convention).
<sub>Last reviewed commit: 5f6fa36</sub>
<!-- greptile_other_comments_section -->
<sub>(3/5) Reply to the agent's comments like "Can you suggest a fix for this @greptileai?" or ask follow-up questions!</sub>
**Context used:**
- Rule from `dashboard` - AGENTS.md ([source](https://app.greptile.com/review/custom-context?memory=09330bde-2058-497c-9c64-ceae637fb5b2))
<!-- /greptile_comment -->
---
<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/733
Author: @AdrianBonpin
Created: 3/3/2026
Status: ✅ Merged
Merged: 3/5/2026
Merged by: @Siumauricio
Base:
canary← Head:tuwunel📝 Commits (3)
fdeef0efeat: add tuwunel template for matrix5f6fa36fix: replace HTML placeholder with actual SVG logo for tuwunel0b7cef6fix: remove enforcement and rename logo📊 Changes
4 files changed (+73 additions, -18 deletions)
View changed files
➕
blueprints/tuwunel/docker-compose.yml(+18 -0)➕
blueprints/tuwunel/template.toml(+15 -0)➕
blueprints/tuwunel/tuwunel.svg(+4 -0)📝
meta.json(+36 -18)📄 Description
What is this PR about?
Remake of PR to add tuwunel (matrix backend)
Checklist
Before submitting this PR, please make sure that:
Issues related (if applicable)
Close automatically the related issues using the keywords:
closes #ISSUE_NUMBERScreenshots or Videos
Greptile Summary
This PR adds a new Tuwunel blueprint — a Rust-based Matrix homeserver — with a
docker-compose.yml,template.toml,logo.svg, and the correspondingmeta.jsonentry. The overall structure follows repository conventions, the image is pinned to a specific version, and thestrapi/streamflowreorder inmeta.jsonis a correct alphabetical fix from runningdedupe-and-sort-meta.js.Issues found:
template.tomlhardcodesTUWUNEL_ALLOW_REGISTRATION=true, silently overriding thefalsedefault indocker-compose.yml. This means every deployment ships with registration turned on. Even though a random token is generated, it is exposed in the deployment configuration. The safer default isfalse, letting operators opt-in after deployment.logo.svginstead oftuwunel.svg. All other blueprints name their logo after the application (e.g.,ghost.jpeg,strapi.svg), per the conventions inAGENTS.md.Confidence Score: 3/5
TUWUNEL_ALLOW_REGISTRATION=truecontradicts the saferfalsedefault in the compose file and poses a security concern for a self-hosted Matrix server. The logo naming deviation is minor but should also be fixed before merging.blueprints/tuwunel/template.toml(registration default) andblueprints/tuwunel/logo.svg/meta.json(logo filename convention).Last reviewed commit:
5f6fa36(3/5) Reply to the agent's comments like "Can you suggest a fix for this @greptileai?" or ask follow-up questions!
Context used:
dashboard- AGENTS.md (source)🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.