Runtime smoke test with generated Dokploy-style env/mount harness: all 9 services started, Postgres became healthy, Taiga frontend returned HTTP 200 through nginx, and /api/v1/ returned HTTP 200 JSON after migrations completed.
Runtime note: local Docker test was run on Apple Silicon through Colima, so Docker reported expected amd64 image emulation warnings for Taiga images. The stack still booted and responded successfully.
🔄 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/895
**Author:** [@rjnevins](https://github.com/rjnevins)
**Created:** 5/21/2026
**Status:** ✅ Merged
**Merged:** 7/7/2026
**Merged by:** [@Siumauricio](https://github.com/Siumauricio)
**Base:** `canary` ← **Head:** `bounty/dokploy-taiga-template`
---
### 📝 Commits (1)
- [`ae09881`](https://github.com/Dokploy/templates/commit/ae0988130f14af594a78e7aa69abb026d704384a) feat: add Taiga template
### 📊 Changes
**4 files changed** (+277 additions, -0 deletions)
<details>
<summary>View changed files</summary>
➕ `blueprints/taiga/docker-compose.yml` (+145 -0)
➕ `blueprints/taiga/logo.png` (+0 -0)
➕ `blueprints/taiga/template.toml` (+114 -0)
📝 `meta.json` (+18 -0)
</details>
### 📄 Description
## What is this PR about?
New PR of Taiga template.
This adds a Dokploy template for Taiga, including:
- Taiga backend, async worker, frontend, events, protected attachments, Postgres, RabbitMQ, and nginx gateway services
- Dokploy-managed environment variables for domain, secrets, Postgres, RabbitMQ, email, telemetry, and registration settings
- nginx gateway config provided through `config.mounts`
- `meta.json` entry and template logo
## 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.
- [x] I have added tests that demonstrate that my correction works or that my new feature works.
Validation run locally:
- `node build-scripts/process-meta.js --input meta.json --output /tmp/meta-out.json --verbose`
- `diff -u meta.json /tmp/meta-out.json`
- `npx --yes tsx build-scripts/validate-template.ts --dir blueprints/taiga --verbose`
- `npx --yes tsx build-scripts/validate-docker-compose.ts --file blueprints/taiga/docker-compose.yml --verbose`
- `docker compose -f blueprints/taiga/docker-compose.yml config`
- Runtime smoke test with generated Dokploy-style env/mount harness: all 9 services started, Postgres became healthy, Taiga frontend returned HTTP 200 through nginx, and `/api/v1/` returned HTTP 200 JSON after migrations completed.
Runtime note: local Docker test was run on Apple Silicon through Colima, so Docker reported expected amd64 image emulation warnings for Taiga images. The stack still booted and responded successfully.
## Issues related (if applicable)
Related to #152
## Screenshots or Videos
N/A
---
<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/895
Author: @rjnevins
Created: 5/21/2026
Status: ✅ Merged
Merged: 7/7/2026
Merged by: @Siumauricio
Base:
canary← Head:bounty/dokploy-taiga-template📝 Commits (1)
ae09881feat: add Taiga template📊 Changes
4 files changed (+277 additions, -0 deletions)
View changed files
➕
blueprints/taiga/docker-compose.yml(+145 -0)➕
blueprints/taiga/logo.png(+0 -0)➕
blueprints/taiga/template.toml(+114 -0)📝
meta.json(+18 -0)📄 Description
What is this PR about?
New PR of Taiga template.
This adds a Dokploy template for Taiga, including:
config.mountsmeta.jsonentry and template logoChecklist
Before submitting this PR, please make sure that:
Validation run locally:
node build-scripts/process-meta.js --input meta.json --output /tmp/meta-out.json --verbosediff -u meta.json /tmp/meta-out.jsonnpx --yes tsx build-scripts/validate-template.ts --dir blueprints/taiga --verbosenpx --yes tsx build-scripts/validate-docker-compose.ts --file blueprints/taiga/docker-compose.yml --verbosedocker compose -f blueprints/taiga/docker-compose.yml config/api/v1/returned HTTP 200 JSON after migrations completed.Runtime note: local Docker test was run on Apple Silicon through Colima, so Docker reported expected amd64 image emulation warnings for Taiga images. The stack still booted and responded successfully.
Issues related (if applicable)
Related to #152
Screenshots or Videos
N/A
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.