github-starred/templates
2
0
Fork 1
mirror of https://github.com/Dokploy/templates.git synced 2026-05-22 14:33:27 -05:00
Code Issues 1.7k Packages Projects Releases Wiki Activity

[PR #811] fix(postiz): add temporal worker and UI services to postiz template #4283

New Issue
Open
opened 2026-04-30 06:51:25 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-30 06:51:25 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/Dokploy/templates/pull/811
Author: @chahat1709
Created: 4/19/2026
Status: 🔄 Open

Base: main ← Head: fix-postiz-temporal

📝 Commits (10+)

  • 1e21b7e feat(librechat): add LibreChat blueprint with compose, toml, metadata, links and tags
  • 758cf1d fix: rename templates to template.toml
  • 47daea9 fix(librechat): rename api service to librechat in docker-compose.yml
  • 3e8b431 Update blueprints/librechat/template.toml
  • 60796a9 Update blueprints/librechat/template.toml
  • 1d70294 fix(librechat): add version under [config] and remove stray [config.mounts] header
  • 2e1fb3b fix(librechat): remove predefined persistent volume mounts from template.toml
  • 46dc5b9 docs(librechat): add authentication reference link to docker-compose.yml
  • ac07aa2 feat: add Rote template
  • d58cc15 fix: process meta.json to fix formatting and sorting

📊 Changes

26 files changed (+968 additions, -91 deletions)

View changed files

📝 blueprints/convex/docker-compose.yml (+8 -8)
📝 blueprints/evolutionapi/docker-compose.yml (+1 -1)
📝 blueprints/grafana/docker-compose.yml (+1 -1)
➕ blueprints/imgproxy/docker-compose.yml (+76 -0)
➕ blueprints/imgproxy/imgproxy.png (+0 -0)
➕ blueprints/imgproxy/template.toml (+56 -0)
➕ blueprints/mediafetch/docker-compose.yml (+18 -0)
➕ blueprints/mediafetch/mediafetch.svg (+1 -0)
➕ blueprints/mediafetch/template.toml (+15 -0)
📝 blueprints/nextcloud-aio/docker-compose.yml (+14 -12)
➖ blueprints/nextcloud-aio/nextcloud-aio.svg (+0 -1)
➕ blueprints/nextcloud-aio/nextcloud.png (+0 -0)
📝 blueprints/nextcloud-aio/template.toml (+166 -12)
📝 blueprints/notifuse/docker-compose.yml (+28 -30)
📝 blueprints/notifuse/template.toml (+2 -17)
📝 blueprints/postiz/docker-compose.yml (+53 -4)
➕ blueprints/tuwunel/docker-compose.yml (+18 -0)
➕ blueprints/tuwunel/template.toml (+15 -0)
➕ blueprints/tuwunel/tuwunel.svg (+4 -0)
➕ blueprints/unleash/docker-compose.yml (+49 -0)

...and 6 more files

📄 Description

This PR adds the requisite Temporal containers (postiz-temporal, postiz-temporal-ui, postiz-temporal-postgres) to the postiz docker-compose blueprint. This addresses the missing task orchestration capabilities originally missing from the template. Healthchecks have been mapped correctly across the cluster for startup synchronization.

Greptile Summary

This PR adds postiz-temporal, postiz-temporal-ui, and postiz-temporal-postgres services to the postiz blueprint to enable Temporal workflow orchestration. The healthcheck dependency chain is wired correctly, but there are two functional issues that would prevent a successful deployment.

  • temporalio/auto-setup is officially deprecated on Docker Hub and is no longer receiving updates or security patches; the Temporal project now recommends temporalio/server + temporalio/admin-tools.
  • DYNAMIC_CONFIG_FILE_PATH=config/dynamicconfig/production-sql.yaml references a file that does not ship with the auto-setup image (only development-sql.yaml is bundled). This will cause Temporal to fail at startup and cascade the failure to postiz-app via its service_healthy dependency, making the entire stack undeployable.

Confidence Score: 3/5

Not safe to merge — two P1 issues (deprecated image and missing dynamic config file) will prevent the postiz stack from starting successfully.

The production-sql.yaml config path points to a file that does not exist in the Temporal image, and the auto-setup image itself is deprecated. Both are P1 findings on the primary changed file that will cause the template to fail on deployment.

blueprints/postiz/docker-compose.yml — the Temporal service configuration needs the dynamic config path corrected and the deprecated image addressed.

Security Review
  • Using the deprecated temporalio/auto-setup image (blueprints/postiz/docker-compose.yml, line 33) means no future CVE patches will be applied to this image layer, increasing long-term exposure risk for deployed instances.

Comments Outside Diff (1)

  1. blueprints/postiz/template.toml, line 1-22 (link)

    P2 postiz-temporal-ui service has no domain mapping

    The postiz-temporal-ui service (running on port 8080) is added to the compose file but template.toml has no corresponding [[config.domains]] entry for it. Users deploying via Dokploy will have no way to access the Temporal web UI without manually adding a domain. If exposing the UI is intentional, add a domain entry; if it's meant to be internal-only, a comment in the compose file would help clarify intent.

Reviews (1): Last reviewed commit: "fix(postiz): Address AI review feedback,..." | Re-trigger Greptile

Greptile also left 3 inline comments on this PR.

Context used:

  • Context used - AGENTS.md (source)

🔄 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/811 **Author:** [@chahat1709](https://github.com/chahat1709) **Created:** 4/19/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `fix-postiz-temporal` --- ### 📝 Commits (10+) - [`1e21b7e`](https://github.com/Dokploy/templates/commit/1e21b7e785b5a2e1b5a604df57cd23d31a0d3955) feat(librechat): add LibreChat blueprint with compose, toml, metadata, links and tags - [`758cf1d`](https://github.com/Dokploy/templates/commit/758cf1d873d45ea0771c109cbcb6101fedc3ba79) fix: rename templates to template.toml - [`47daea9`](https://github.com/Dokploy/templates/commit/47daea92f862cf2d111d017b6f3e9da176455451) fix(librechat): rename api service to librechat in docker-compose.yml - [`3e8b431`](https://github.com/Dokploy/templates/commit/3e8b43103173503b19e93276aa9810f4fa8cba98) Update blueprints/librechat/template.toml - [`60796a9`](https://github.com/Dokploy/templates/commit/60796a90847bf27061eaba5491eb02c49400bdf2) Update blueprints/librechat/template.toml - [`1d70294`](https://github.com/Dokploy/templates/commit/1d702943103d80af380e68f9a274d14d2fd90223) fix(librechat): add version under [config] and remove stray [config.mounts] header - [`2e1fb3b`](https://github.com/Dokploy/templates/commit/2e1fb3b3a9ea2c277d593ca5891e744b0c01a7f6) fix(librechat): remove predefined persistent volume mounts from template.toml - [`46dc5b9`](https://github.com/Dokploy/templates/commit/46dc5b9be3ea8f06d931d709ded142d2f7a216a9) docs(librechat): add authentication reference link to docker-compose.yml - [`ac07aa2`](https://github.com/Dokploy/templates/commit/ac07aa2ed86c1ff47af34a3e50533ea2ce4946ff) feat: add Rote template - [`d58cc15`](https://github.com/Dokploy/templates/commit/d58cc15c54c09f2e8a5768c839d569a2d2d61ce0) fix: process meta.json to fix formatting and sorting ### 📊 Changes **26 files changed** (+968 additions, -91 deletions) <details> <summary>View changed files</summary> 📝 `blueprints/convex/docker-compose.yml` (+8 -8) 📝 `blueprints/evolutionapi/docker-compose.yml` (+1 -1) 📝 `blueprints/grafana/docker-compose.yml` (+1 -1) ➕ `blueprints/imgproxy/docker-compose.yml` (+76 -0) ➕ `blueprints/imgproxy/imgproxy.png` (+0 -0) ➕ `blueprints/imgproxy/template.toml` (+56 -0) ➕ `blueprints/mediafetch/docker-compose.yml` (+18 -0) ➕ `blueprints/mediafetch/mediafetch.svg` (+1 -0) ➕ `blueprints/mediafetch/template.toml` (+15 -0) 📝 `blueprints/nextcloud-aio/docker-compose.yml` (+14 -12) ➖ `blueprints/nextcloud-aio/nextcloud-aio.svg` (+0 -1) ➕ `blueprints/nextcloud-aio/nextcloud.png` (+0 -0) 📝 `blueprints/nextcloud-aio/template.toml` (+166 -12) 📝 `blueprints/notifuse/docker-compose.yml` (+28 -30) 📝 `blueprints/notifuse/template.toml` (+2 -17) 📝 `blueprints/postiz/docker-compose.yml` (+53 -4) ➕ `blueprints/tuwunel/docker-compose.yml` (+18 -0) ➕ `blueprints/tuwunel/template.toml` (+15 -0) ➕ `blueprints/tuwunel/tuwunel.svg` (+4 -0) ➕ `blueprints/unleash/docker-compose.yml` (+49 -0) _...and 6 more files_ </details> ### 📄 Description This PR adds the requisite Temporal containers (postiz-temporal, postiz-temporal-ui, postiz-temporal-postgres) to the postiz docker-compose blueprint. This addresses the missing task orchestration capabilities originally missing from the template. Healthchecks have been mapped correctly across the cluster for startup synchronization. <!-- greptile_comment --> <h3>Greptile Summary</h3> This PR adds `postiz-temporal`, `postiz-temporal-ui`, and `postiz-temporal-postgres` services to the postiz blueprint to enable Temporal workflow orchestration. The healthcheck dependency chain is wired correctly, but there are two functional issues that would prevent a successful deployment. - `temporalio/auto-setup` is officially deprecated on Docker Hub and is no longer receiving updates or security patches; the Temporal project now recommends `temporalio/server` + `temporalio/admin-tools`. - `DYNAMIC_CONFIG_FILE_PATH=config/dynamicconfig/production-sql.yaml` references a file that does not ship with the `auto-setup` image (only `development-sql.yaml` is bundled). This will cause Temporal to fail at startup and cascade the failure to `postiz-app` via its `service_healthy` dependency, making the entire stack undeployable. <h3>Confidence Score: 3/5</h3> Not safe to merge — two P1 issues (deprecated image and missing dynamic config file) will prevent the postiz stack from starting successfully. The `production-sql.yaml` config path points to a file that does not exist in the Temporal image, and the `auto-setup` image itself is deprecated. Both are P1 findings on the primary changed file that will cause the template to fail on deployment. `blueprints/postiz/docker-compose.yml` — the Temporal service configuration needs the dynamic config path corrected and the deprecated image addressed. <details open><summary><h3>Security Review</h3></summary> - Using the deprecated `temporalio/auto-setup` image (`blueprints/postiz/docker-compose.yml`, line 33) means no future CVE patches will be applied to this image layer, increasing long-term exposure risk for deployed instances. </details> <!-- greptile_failed_comments --> <details><summary><h3>Comments Outside Diff (1)</h3></summary> 1. `blueprints/postiz/template.toml`, line 1-22 ([link](https://github.com/dokploy/templates/blob/a39a5f2e34f3ed94710b225490c317df47eb47e7/blueprints/postiz/template.toml#L1-L22)) <a href="#"><img alt="P2" src="https://greptile-static-assets.s3.amazonaws.com/badges/p2.svg?v=7" align="top"></a> **`postiz-temporal-ui` service has no domain mapping** The `postiz-temporal-ui` service (running on port 8080) is added to the compose file but `template.toml` has no corresponding `[[config.domains]]` entry for it. Users deploying via Dokploy will have no way to access the Temporal web UI without manually adding a domain. If exposing the UI is intentional, add a domain entry; if it's meant to be internal-only, a comment in the compose file would help clarify intent. </details> <!-- /greptile_failed_comments --> <sub>Reviews (1): Last reviewed commit: ["fix(postiz): Address AI review feedback,..."](https://github.com/dokploy/templates/commit/a39a5f2e34f3ed94710b225490c317df47eb47e7) | [Re-trigger Greptile](https://app.greptile.com/api/retrigger?id=28894731)</sub> > Greptile also left **3 inline comments** on this PR. **Context used:** - Context 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>
GiteaMirror added the pull-request label 2026-04-30 06:51:25 -05: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#4283
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?