add a new triggerdotdev-v4 blueprint with a full Trigger.dev v4 stack (Trigger app, Supervisor, PostgreSQL, Redis, ElectricSQL, ClickHouse, MinIO, registry, and docker socket proxy)
add template.yml variables, domain wiring, and generated secrets needed for Dokploy setup
include clickhouse/override.xml via template mounts and register the template in meta.json with a dedicated logo
Notes
DOCKER_RUNNER_NETWORKS defaults to set-after-first-deploy; set it to your Dokploy network name after first deployment for managed worker runs
Greptile Summary
Adds a comprehensive Trigger.dev v4 self-hosting template with 10 services (Trigger app, Supervisor, PostgreSQL, Redis, ElectricSQL, ClickHouse, MinIO, Docker registry, registry-init, docker-socket-proxy). The template uses proper secret generation and domain wiring via template.yml.
Missing version: "3.8" in docker-compose.yml — required by repository conventions (AGENTS.md)
Unpinned Docker images — bitnamilegacy/clickhouse:latest, bitnamilegacy/minio:latest, tecnativa/docker-socket-proxy:latest, and httpd:alpine should be pinned to specific versions per security guidelines
Redundant Docker socket mount on supervisor service — the direct /var/run/docker.sock mount bypasses the docker-proxy access controls, while DOCKER_HOST is already configured to use the proxy
Template configuration (template.yml), meta.json entry, and SVG logo are well-structured and follow repository patterns
Confidence Score: 3/5
Functional but has convention violations and a potential security concern with the redundant Docker socket mount
Score of 3 reflects that while the template is comprehensive and mostly well-structured, it has a missing required version field, multiple unpinned :latest Docker images against security policy, and a redundant Docker socket mount that bypasses proxy access controls. These should be addressed before merging.
Pay close attention to blueprints/triggerdotdev-v4/docker-compose.yml — it has the missing version field, unpinned images, and the redundant Docker socket mount on the supervisor service
🔄 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/745
**Author:** [@digitalbase](https://github.com/digitalbase)
**Created:** 3/15/2026
**Status:** 🔄 Open
**Base:** `main` ← **Head:** `trigger-v4-template-dokploy`
---
### 📝 Commits (8)
- [`6f774f0`](https://github.com/Dokploy/templates/commit/6f774f09186d8e8220ff0edce8636d5247c78e2d) feat: add Trigger.dev v4 template
- [`9f63eb4`](https://github.com/Dokploy/templates/commit/9f63eb49927a88a09a5683c2bfb41864872837d8) refactor(triggerdotdev-v4): use template.toml config
- [`f9e0ace`](https://github.com/Dokploy/templates/commit/f9e0ace7725044b3252b9c0b27f0a951ad1bc4f9) fix(triggerdotdev-v4): add compose version and use socket proxy only
- [`38f07ac`](https://github.com/Dokploy/templates/commit/38f07ac88aa6ffc299997efa470b321c727f75c6) chore(triggerdotdev-v4): pin images and target v4.4.3
- [`273abda`](https://github.com/Dokploy/templates/commit/273abdaafe389da9a8b6fee51170ef61e486276b) fix(triggerdotdev-v4): enforce 32-byte encryption key and wait for worker token
- [`8312eb0`](https://github.com/Dokploy/templates/commit/8312eb0a4acc21490f008550de273d2c45663fa0) fix(triggerdotdev-v4): remove unsupported clickhouse secure URL param
- [`c96fee9`](https://github.com/Dokploy/templates/commit/c96fee9c1f428dd3c98b5b224df71cb9743ce25b) fix(triggerdotdev-v4): split clickhouse URLs for migrations and query client
- [`4fd02b5`](https://github.com/Dokploy/templates/commit/4fd02b56a5909ed3136bdc13c6f0151dbdf56c3e) chore(triggerdotdev-v4): expose main domain as runtime env var
### 📊 Changes
**4 files changed** (+343 additions, -1 deletions)
<details>
<summary>View changed files</summary>
➕ `blueprints/triggerdotdev-v4/docker-compose.yml` (+247 -0)
➕ `blueprints/triggerdotdev-v4/template.toml` (+67 -0)
➕ `blueprints/triggerdotdev-v4/triggerdotdev-v4.svg` (+11 -0)
📝 `meta.json` (+18 -1)
</details>
### 📄 Description
## Summary
- add a new `triggerdotdev-v4` blueprint with a full Trigger.dev v4 stack (Trigger app, Supervisor, PostgreSQL, Redis, ElectricSQL, ClickHouse, MinIO, registry, and docker socket proxy)
- add `template.yml` variables, domain wiring, and generated secrets needed for Dokploy setup
- include `clickhouse/override.xml` via template mounts and register the template in `meta.json` with a dedicated logo
## Notes
- `DOCKER_RUNNER_NETWORKS` defaults to `set-after-first-deploy`; set it to your Dokploy network name after first deployment for managed worker runs
<!-- greptile_comment -->
<h3>Greptile Summary</h3>
Adds a comprehensive Trigger.dev v4 self-hosting template with 10 services (Trigger app, Supervisor, PostgreSQL, Redis, ElectricSQL, ClickHouse, MinIO, Docker registry, registry-init, docker-socket-proxy). The template uses proper secret generation and domain wiring via `template.yml`.
- **Missing `version: "3.8"`** in `docker-compose.yml` — required by repository conventions (AGENTS.md)
- **Unpinned Docker images** — `bitnamilegacy/clickhouse:latest`, `bitnamilegacy/minio:latest`, `tecnativa/docker-socket-proxy:latest`, and `httpd:alpine` should be pinned to specific versions per security guidelines
- **Redundant Docker socket mount** on `supervisor` service — the direct `/var/run/docker.sock` mount bypasses the `docker-proxy` access controls, while `DOCKER_HOST` is already configured to use the proxy
- Template configuration (`template.yml`), meta.json entry, and SVG logo are well-structured and follow repository patterns
<h3>Confidence Score: 3/5</h3>
- Functional but has convention violations and a potential security concern with the redundant Docker socket mount
- Score of 3 reflects that while the template is comprehensive and mostly well-structured, it has a missing required version field, multiple unpinned :latest Docker images against security policy, and a redundant Docker socket mount that bypasses proxy access controls. These should be addressed before merging.
- Pay close attention to `blueprints/triggerdotdev-v4/docker-compose.yml` — it has the missing version field, unpinned images, and the redundant Docker socket mount on the supervisor service
<sub>Last reviewed commit: 6f774f0</sub>
> Greptile also left **3 inline comments** on this PR.
<sub>(2/5) Greptile learns from your feedback when you react with thumbs up/down!</sub>
**Context used:**
- Rule used - 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/745
Author: @digitalbase
Created: 3/15/2026
Status: 🔄 Open
Base:
main← Head:trigger-v4-template-dokploy📝 Commits (8)
6f774f0feat: add Trigger.dev v4 template9f63eb4refactor(triggerdotdev-v4): use template.toml configf9e0acefix(triggerdotdev-v4): add compose version and use socket proxy only38f07acchore(triggerdotdev-v4): pin images and target v4.4.3273abdafix(triggerdotdev-v4): enforce 32-byte encryption key and wait for worker token8312eb0fix(triggerdotdev-v4): remove unsupported clickhouse secure URL paramc96fee9fix(triggerdotdev-v4): split clickhouse URLs for migrations and query client4fd02b5chore(triggerdotdev-v4): expose main domain as runtime env var📊 Changes
4 files changed (+343 additions, -1 deletions)
View changed files
➕
blueprints/triggerdotdev-v4/docker-compose.yml(+247 -0)➕
blueprints/triggerdotdev-v4/template.toml(+67 -0)➕
blueprints/triggerdotdev-v4/triggerdotdev-v4.svg(+11 -0)📝
meta.json(+18 -1)📄 Description
Summary
triggerdotdev-v4blueprint with a full Trigger.dev v4 stack (Trigger app, Supervisor, PostgreSQL, Redis, ElectricSQL, ClickHouse, MinIO, registry, and docker socket proxy)template.ymlvariables, domain wiring, and generated secrets needed for Dokploy setupclickhouse/override.xmlvia template mounts and register the template inmeta.jsonwith a dedicated logoNotes
DOCKER_RUNNER_NETWORKSdefaults toset-after-first-deploy; set it to your Dokploy network name after first deployment for managed worker runsGreptile Summary
Adds a comprehensive Trigger.dev v4 self-hosting template with 10 services (Trigger app, Supervisor, PostgreSQL, Redis, ElectricSQL, ClickHouse, MinIO, Docker registry, registry-init, docker-socket-proxy). The template uses proper secret generation and domain wiring via
template.yml.version: "3.8"indocker-compose.yml— required by repository conventions (AGENTS.md)bitnamilegacy/clickhouse:latest,bitnamilegacy/minio:latest,tecnativa/docker-socket-proxy:latest, andhttpd:alpineshould be pinned to specific versions per security guidelinessupervisorservice — the direct/var/run/docker.sockmount bypasses thedocker-proxyaccess controls, whileDOCKER_HOSTis already configured to use the proxytemplate.yml), meta.json entry, and SVG logo are well-structured and follow repository patternsConfidence Score: 3/5
blueprints/triggerdotdev-v4/docker-compose.yml— it has the missing version field, unpinned images, and the redundant Docker socket mount on the supervisor serviceLast reviewed commit:
6f774f0(2/5) Greptile learns from your feedback when you react with thumbs up/down!
Context used:
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.