Skip to content

Add Taiga template#895

Open
rjnevins wants to merge 1 commit into
Dokploy:canaryfrom
rjnevins:bounty/dokploy-taiga-template
Open

Add Taiga template#895
rjnevins wants to merge 1 commit into
Dokploy:canaryfrom
rjnevins:bounty/dokploy-taiga-template

Conversation

@rjnevins
Copy link
Copy Markdown

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:

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

Adds a Dokploy template for Taiga (taigaio/taiga-back, taiga-front,
taiga-events, taiga-protected) wired through an nginx gateway, with
RabbitMQ and Postgres backing services.

Diverges from prior PR Dokploy#547 in two ways:
- Strips trailing inline `# ...` comments from env values in
  template.toml. Those comments were captured as part of the value when
  Dokploy expanded them into docker-compose, polluting strings like
  TAIGA_SCHEME, EMAIL_BACKEND, etc. and breaking Django URL/email
  configuration at runtime.
- Adds explicit SUBPATH= and RABBITMQ_VHOST env entries that PR Dokploy#547
  referenced but never set, so variable expansion no longer falls back
  to empty/undefined.

Validated locally with build-scripts/validate-template.ts,
build-scripts/validate-docker-compose.ts, and meta.json required-field
+ dedupe-and-sort checks. No runtime deploy was performed locally.
@dosubot dosubot Bot added size:L This PR changes 100-499 lines, ignoring generated files. new-template labels May 21, 2026
@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 21, 2026

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Name Status Preview Last Commit
templates ✅ Ready (View Log) Visit Preview ae09881

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

new-template size:L This PR changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant