9430a34 fix(postiz): remove missing dynamic config reference from temporal service
📊 Changes
1 file changed (+49 additions, -4 deletions)
View changed files
📝blueprints/postiz/docker-compose.yml (+49 -4)
📄 Description
Resolves an issue where the Temporal auto-setup script fails to start due to schema contention with the main Postiz backend. This adds a dedicated Temporal Postgres service and the Temporal Web UI for workflow monitoring.
Greptile Summary
This PR correctly isolates Temporal's schema into its own dedicated PostgreSQL instance (postiz-temporal-postgres) to fix the schema contention crash loop, and adds the Temporal Web UI for monitoring. However, the healthcheck on postiz-temporal uses tctl, which is only available in the temporalio/admin-tools image — not in temporalio/auto-setup. The container will never report healthy, and postiz-app (which depends on condition: service_healthy) will never start.
P1 — tctl is absent from temporalio/auto-setup:1.27.2; replace the healthcheck with a TCP probe (nc -z localhost 7233) so the dependency chain can resolve.
P2 — temporalio/auto-setup is officially deprecated on Docker Hub; a follow-up migration to temporalio/server + temporalio/admin-tools is recommended.
Confidence Score: 4/5
Not safe to merge as-is — the broken healthcheck prevents postiz-app from ever starting.
The architectural fix (dedicated Temporal Postgres) is correct, but the P1 healthcheck bug using a non-existent binary (tctl) in the auto-setup container will block postiz-app from starting entirely. One targeted fix to the healthcheck command is needed before this is mergeable.
blueprints/postiz/docker-compose.yml — specifically the healthcheck.test on the postiz-temporal service (line 46).
🔄 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/800
**Author:** [@chahat1709](https://github.com/chahat1709)
**Created:** 4/17/2026
**Status:** 🔄 Open
**Base:** `canary` ← **Head:** `fix-postiz-temporal`
---
### 📝 Commits (4)
- [`080cd86`](https://github.com/Dokploy/templates/commit/080cd869b9643974b81cd5ee1ce1519343209d26) fix(postiz): Resolve Temporal crash loop by isolating Workflow database
- [`a39a5f2`](https://github.com/Dokploy/templates/commit/a39a5f2e34f3ed94710b225490c317df47eb47e7) fix(postiz): Address AI review feedback, update healthcheck and configs
- [`3abfbe5`](https://github.com/Dokploy/templates/commit/3abfbe50251a7ff25eee69e19ba772764b4f0876) fix(postiz): use temporalio/server image, add dynamic config volume, fix healthcheck
- [`9430a34`](https://github.com/Dokploy/templates/commit/9430a343d19e22edadeb48a96f1b9b1b7be60871) fix(postiz): remove missing dynamic config reference from temporal service
### 📊 Changes
**1 file changed** (+49 additions, -4 deletions)
<details>
<summary>View changed files</summary>
📝 `blueprints/postiz/docker-compose.yml` (+49 -4)
</details>
### 📄 Description
Resolves an issue where the Temporal auto-setup script fails to start due to schema contention with the main Postiz backend. This adds a dedicated Temporal Postgres service and the Temporal Web UI for workflow monitoring.
<!-- greptile_comment -->
<h3>Greptile Summary</h3>
This PR correctly isolates Temporal's schema into its own dedicated PostgreSQL instance (`postiz-temporal-postgres`) to fix the schema contention crash loop, and adds the Temporal Web UI for monitoring. However, the healthcheck on `postiz-temporal` uses `tctl`, which is only available in the `temporalio/admin-tools` image — not in `temporalio/auto-setup`. The container will never report healthy, and `postiz-app` (which depends on `condition: service_healthy`) will never start.
- **P1** — `tctl` is absent from `temporalio/auto-setup:1.27.2`; replace the healthcheck with a TCP probe (`nc -z localhost 7233`) so the dependency chain can resolve.
- **P2** — `temporalio/auto-setup` is officially deprecated on Docker Hub; a follow-up migration to `temporalio/server` + `temporalio/admin-tools` is recommended.
<h3>Confidence Score: 4/5</h3>
Not safe to merge as-is — the broken healthcheck prevents postiz-app from ever starting.
The architectural fix (dedicated Temporal Postgres) is correct, but the P1 healthcheck bug using a non-existent binary (tctl) in the auto-setup container will block postiz-app from starting entirely. One targeted fix to the healthcheck command is needed before this is mergeable.
blueprints/postiz/docker-compose.yml — specifically the healthcheck.test on the postiz-temporal service (line 46).
<sub>Reviews (1): Last reviewed commit: ["fix(postiz): Resolve Temporal crash loop..."](https://github.com/dokploy/templates/commit/080cd869b9643974b81cd5ee1ce1519343209d26) | [Re-trigger Greptile](https://app.greptile.com/api/retrigger?id=28765322)</sub>
> Greptile also left **2 inline comments** on this PR.
<!-- /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/800
Author: @chahat1709
Created: 4/17/2026
Status: 🔄 Open
Base:
canary← Head:fix-postiz-temporal📝 Commits (4)
080cd86fix(postiz): Resolve Temporal crash loop by isolating Workflow databasea39a5f2fix(postiz): Address AI review feedback, update healthcheck and configs3abfbe5fix(postiz): use temporalio/server image, add dynamic config volume, fix healthcheck9430a34fix(postiz): remove missing dynamic config reference from temporal service📊 Changes
1 file changed (+49 additions, -4 deletions)
View changed files
📝
blueprints/postiz/docker-compose.yml(+49 -4)📄 Description
Resolves an issue where the Temporal auto-setup script fails to start due to schema contention with the main Postiz backend. This adds a dedicated Temporal Postgres service and the Temporal Web UI for workflow monitoring.
Greptile Summary
This PR correctly isolates Temporal's schema into its own dedicated PostgreSQL instance (
postiz-temporal-postgres) to fix the schema contention crash loop, and adds the Temporal Web UI for monitoring. However, the healthcheck onpostiz-temporalusestctl, which is only available in thetemporalio/admin-toolsimage — not intemporalio/auto-setup. The container will never report healthy, andpostiz-app(which depends oncondition: service_healthy) will never start.tctlis absent fromtemporalio/auto-setup:1.27.2; replace the healthcheck with a TCP probe (nc -z localhost 7233) so the dependency chain can resolve.temporalio/auto-setupis officially deprecated on Docker Hub; a follow-up migration totemporalio/server+temporalio/admin-toolsis recommended.Confidence Score: 4/5
Not safe to merge as-is — the broken healthcheck prevents postiz-app from ever starting.
The architectural fix (dedicated Temporal Postgres) is correct, but the P1 healthcheck bug using a non-existent binary (tctl) in the auto-setup container will block postiz-app from starting entirely. One targeted fix to the healthcheck command is needed before this is mergeable.
blueprints/postiz/docker-compose.yml — specifically the healthcheck.test on the postiz-temporal service (line 46).
Reviews (1): Last reviewed commit: "fix(postiz): Resolve Temporal crash loop..." | Re-trigger Greptile
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.