[PR #956] [CLOSED] feat: add Taiga template #15286

New Issue

GiteaMirror · 2026-07-13T16:59:38-05:00

GiteaMirror commented

2026-07-13 16:59:38 -05:00

📋 Pull Request Information

Original PR: https://github.com/Dokploy/templates/pull/956
Author: @rohitmulani63-ops
Created: 6/22/2026
Status: ❌ Closed

Base: canary ← Head: add-taiga-template

📝 Commits (3)

b044ff8 feat: add Taiga template
eb57d53 Fix Taiga template metadata and config mount
d98ced1 Merge remote-tracking branch 'origin/canary' into add-taiga-template

📊 Changes

4 files changed (+291 additions, -0 deletions)

View changed files

➕ blueprints/taiga/docker-compose.yml (+158 -0)
➕ blueprints/taiga/taiga.svg (+1 -0)
➕ blueprints/taiga/template.toml (+114 -0)
📝 meta.json (+18 -0)

📄 Description

/claim #152
Closes #692

What is this PR about?

I added a Taiga template based on the upstream Taiga Docker setup. The template includes the web, back, async, events, protected, PostgreSQL, and RabbitMQ services, plus the Dokploy domain and environment wiring needed for deployment.

Checklist

I read the template requirements in the repository README.
I added the template files and metadata.
I ran the template validation checks below.
I tested the template in a running Dokploy instance.

Validation

node dedupe-and-sort-meta.js
npm --prefix build-scripts run validate-template -- --dir ../blueprints/taiga
npm --prefix build-scripts run validate-docker-compose -- --file ../blueprints/taiga/docker-compose.yml
git diff --check

Not run: full Docker runtime smoke test, because Docker is unavailable locally.

_{🔄 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/956 **Author:** [@rohitmulani63-ops](https://github.com/rohitmulani63-ops) **Created:** 6/22/2026 **Status:** ❌ Closed **Base:** `canary` ← **Head:** `add-taiga-template` --- ### 📝 Commits (3) - [`b044ff8`](https://github.com/Dokploy/templates/commit/b044ff872c8dd07372ffdc08dc72e3ad84fa4304) feat: add Taiga template - [`eb57d53`](https://github.com/Dokploy/templates/commit/eb57d531821679182403ffb6db5e7b608084ac65) Fix Taiga template metadata and config mount - [`d98ced1`](https://github.com/Dokploy/templates/commit/d98ced18e6a313f2842f19420fb8f80c4df321e5) Merge remote-tracking branch 'origin/canary' into add-taiga-template ### 📊 Changes **4 files changed** (+291 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `blueprints/taiga/docker-compose.yml` (+158 -0) ➕ `blueprints/taiga/taiga.svg` (+1 -0) ➕ `blueprints/taiga/template.toml` (+114 -0) 📝 `meta.json` (+18 -0) </details> ### 📄 Description /claim #152 Closes #692 ## What is this PR about? I added a Taiga template based on the upstream Taiga Docker setup. The template includes the web, back, async, events, protected, PostgreSQL, and RabbitMQ services, plus the Dokploy domain and environment wiring needed for deployment. ## Checklist - [x] I read the template requirements in the repository README. - [x] I added the template files and metadata. - [x] I ran the template validation checks below. - [ ] I tested the template in a running Dokploy instance. ## Validation - node dedupe-and-sort-meta.js - npm --prefix build-scripts run validate-template -- --dir ../blueprints/taiga - npm --prefix build-scripts run validate-docker-compose -- --file ../blueprints/taiga/docker-compose.yml - git diff --check Not run: full Docker runtime smoke test, because Docker is unavailable locally. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

GiteaMirror added the pull-request label 2026-07-13 16:59:38 -05:00

GiteaMirror closed this issue

2026-07-13 16:59:41 -05:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/templates#15286