feat: add Tandoor Recipes template

[rohitmulani63-ops]

/claim #152

What is this PR about?

This PR adds a new Tandoor Recipes Dokploy template. Adds a Tandoor Recipes template with PostgreSQL, generated secret/password values, persistent media/static volumes, and Dokploy routing on port 8080.

Validation

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

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

Notes

I kept this as a focused single-template PR so it stays easy to review. Maintainer edits are enabled.

[Siumauricio]

Automated template check 🤖

This PR's template was imported into a test Dokploy instance (using the docker-compose.yml + template.toml from the PR head) and deployed, and its configured domains were then checked over HTTP.

Result: ❌ some issues need attention

tandoor-recipes

• Deploy: done (49s)
• Domain checks:
  • tandoor-recipes:8080 → HTTP 502 ❌
• Container states at failure time: tandoor-recipes-1: running · tandoor-db-1: running
• Issues:
  • domain check failed for service tandoor-recipes:8080 (path /): kept returning HTTP 502 for 3 minutes after the deploy finished

The test service is removed automatically after verification. Happy to re-test once the PR is updated.

[github-actions]

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

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

[rohitmulani63-ops]

Thanks for the check, @Siumauricio.

Summary:

• Updated Dokploy routing from 8080 to container port 80, matching the current Tandoor image/docs behavior.
• Added ALLOWED_HOSTS and CSRF_TRUSTED_ORIGINS wiring for the deployed domain.
• Merged the branch with latest canary; the PR is mergeable now.

Validation:

• docker compose -f blueprints/tandoor-recipes/docker-compose.yml config with sample env values
• git diff --check
• GitHub checks are green: validate-meta, validate, validate-docker-compose, and build-preview

Happy to adjust further if the runtime retest shows anything else.

[Siumauricio]

Automated template check 🤖

This PR's template was imported into a test Dokploy instance (using the docker-compose.yml + template.toml from the PR head) and deployed, and its configured domains were then checked over HTTP.

Result: ❌ some issues need attention

tandoor-recipes

• Deploy: done (50s)
• Domain checks:
  • tandoor-recipes:80 → HTTP 502 ❌
• Container states at failure time: tandoor-recipes-1: running · tandoor-db-1: running
• Issues:
  • domain check failed for service tandoor-recipes:80 (path /): kept returning HTTP 502 for 3 minutes after the deploy finished

The test service is removed automatically after verification. Happy to re-test once the PR is updated.

[Siumauricio]

Pushed a fix and deploy-tested it ✅ — the 2.x image binds gunicorn to a unix socket unless TANDOOR_PORT is set, so Traefik was getting 502 on port 80. Now serving HTTP 200 (setup page) on port 8080.

[rohitmulani63-ops]

@algora-pbc /claim #152

This merged PR adds the Tandoor Recipes template under the Dokploy template bounty. Validation and the maintainer deploy-test fix are included in the PR discussion.