github-starred/templates
2
0
Fork 1
mirror of https://github.com/Dokploy/templates.git synced 2026-03-12 01:56:43 -05:00
Code Issues 155 Packages Projects Releases Wiki Activity

[PR #435] Add Trigger.dev V4 template #454

New Issue
Open
opened 2025-11-22 20:38:58 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-22 20:38:58 -06:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/Dokploy/templates/pull/435
Author: @eonminion
Created: 10/8/2025
Status: 🔄 Open

Base: main ← Head: main

📝 Commits (10+)

  • 9f172de feat: add trigger v4
  • 69222a8 fix: add offcial env config
  • 39c1c6d feat: add auth env
  • 641416a fix: pr error
  • ea7e7b3 fix: load error
  • 21c951d refactor: update docker-compose and template configuration
  • 4c76b67 feat: add Trigger.dev V4 Web blueprint with Docker Compose setup
  • f86971b feat: add Trigger.dev V4 Worker blueprint with Docker Compose setup
  • 25f7bbe feat: add DEPLOY_IMAGE_PLATFORM variable to Docker configuration
  • e715114 perf: simplify

📊 Changes

10 files changed (+851 additions, -0 deletions)

View changed files

➕ blueprints/triggerdotdev4-web/docker-compose.yml (+274 -0)
➕ blueprints/triggerdotdev4-web/template.toml (+68 -0)
➕ blueprints/triggerdotdev4-web/triggerdotdev.svg (+2 -0)
➕ blueprints/triggerdotdev4-worker/docker-compose.yml (+83 -0)
➕ blueprints/triggerdotdev4-worker/template.toml (+7 -0)
➕ blueprints/triggerdotdev4-worker/triggerdotdev.svg (+2 -0)
➕ blueprints/triggerdotdev4/docker-compose.yml (+296 -0)
➕ blueprints/triggerdotdev4/template.toml (+69 -0)
➕ blueprints/triggerdotdev4/triggerdotdev.svg (+2 -0)
📝 meta.json (+48 -0)

📄 Description

Tried the existed v3 template, was not able to get it to work, so I made the new template base of the official guide:
https://trigger.dev/docs/self-hosting/docker#setup

There is problems remain unresolved:
Problem 1: Domain/URL not accessible when deploying via template

When I deploy directly using my template, the domain URL fails to open
However, when I manually copy the same docker-compose.yml and .env files into a new compose service and manually configure the domain, it works perfectly
This suggests the template deployment process isn't handling the domain configuration correctly

Problem 2: PostgreSQL username configuration error

When I try to change the PostgreSQL username (from the default), I get this error:

Fatal: role "postgresql" does not exist

It appears the system is still looking for a role named "postgresql" instead of using my custom username

🔄 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/435 **Author:** [@eonminion](https://github.com/eonminion) **Created:** 10/8/2025 **Status:** 🔄 Open **Base:** `main` ← **Head:** `main` --- ### 📝 Commits (10+) - [`9f172de`](https://github.com/Dokploy/templates/commit/9f172de9f9f54d025187ae349f2b1646eba1b1f4) feat: add trigger v4 - [`69222a8`](https://github.com/Dokploy/templates/commit/69222a8d9785df1fd1a3190950d79c63a5cb2839) fix: add offcial env config - [`39c1c6d`](https://github.com/Dokploy/templates/commit/39c1c6de66ff6801863d24a98937d74b1f731910) feat: add auth env - [`641416a`](https://github.com/Dokploy/templates/commit/641416a079a74d89d93932668019f7b8340b28ae) fix: pr error - [`ea7e7b3`](https://github.com/Dokploy/templates/commit/ea7e7b3ae01ab50e80ff54ef9b42e8e1c2eb89ab) fix: load error - [`21c951d`](https://github.com/Dokploy/templates/commit/21c951dba82a46b1f8f9ad31640f820572192c6c) refactor: update docker-compose and template configuration - [`4c76b67`](https://github.com/Dokploy/templates/commit/4c76b674e33278a3d4eae1ac33d1262d45269c34) feat: add Trigger.dev V4 Web blueprint with Docker Compose setup - [`f86971b`](https://github.com/Dokploy/templates/commit/f86971be1075b564b00c020e73a3b62e20a26a68) feat: add Trigger.dev V4 Worker blueprint with Docker Compose setup - [`25f7bbe`](https://github.com/Dokploy/templates/commit/25f7bbe11994e66d26779309e9379bb196967da0) feat: add DEPLOY_IMAGE_PLATFORM variable to Docker configuration - [`e715114`](https://github.com/Dokploy/templates/commit/e715114b23d1e6ec45020a54f01a0c6cc4038828) perf: simplify ### 📊 Changes **10 files changed** (+851 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `blueprints/triggerdotdev4-web/docker-compose.yml` (+274 -0) ➕ `blueprints/triggerdotdev4-web/template.toml` (+68 -0) ➕ `blueprints/triggerdotdev4-web/triggerdotdev.svg` (+2 -0) ➕ `blueprints/triggerdotdev4-worker/docker-compose.yml` (+83 -0) ➕ `blueprints/triggerdotdev4-worker/template.toml` (+7 -0) ➕ `blueprints/triggerdotdev4-worker/triggerdotdev.svg` (+2 -0) ➕ `blueprints/triggerdotdev4/docker-compose.yml` (+296 -0) ➕ `blueprints/triggerdotdev4/template.toml` (+69 -0) ➕ `blueprints/triggerdotdev4/triggerdotdev.svg` (+2 -0) 📝 `meta.json` (+48 -0) </details> ### 📄 Description Tried the existed v3 template, was not able to get it to work, so I made the new template base of the official guide: https://trigger.dev/docs/self-hosting/docker#setup There is problems remain unresolved: Problem 1: Domain/URL not accessible when deploying via template When I deploy directly using my template, the domain URL fails to open However, when I manually copy the same docker-compose.yml and .env files into a new compose service and manually configure the domain, it works perfectly This suggests the template deployment process isn't handling the domain configuration correctly Problem 2: PostgreSQL username configuration error When I try to change the PostgreSQL username (from the default), I get this error: Fatal: role "postgresql" does not exist It appears the system is still looking for a role named "postgresql" instead of using my custom username --- <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 2025-11-22 20:38:58 -06:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
documentation
pull-request
Mirrored from GitHub Pull Request
 template
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/templates#454
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?