fix(postiz): Resolve Temporal crash loop by isolating Workflow database by chahat1709 · Pull Request #800 · Dokploy/templates

chahat1709 · 2026-04-17T12:43:33Z

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).

_{Reviews (1): Last reviewed commit: "fix(postiz): Resolve Temporal crash loop..." | Re-trigger Greptile}

Greptile also left 2 inline comments on this PR.

github-actions · 2026-04-17T12:44:24Z

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Name	Status	Preview	Last Commit
templates	✅ Ready (View Log)	Visit Preview	`64e2d72`

Copilot

Pull request overview

This PR aims to stop Postiz’s Temporal component from crash-looping by isolating Temporal onto its own Postgres instance, and it introduces a Temporal Web UI service for workflow monitoring.

Changes:

Added dedicated Temporal services (temporalio/auto-setup, temporalio/ui) plus a separate Postgres instance for Temporal persistence.
Wired Postiz to Temporal via new environment variables and added depends_on health-based startup ordering.
Added a new persistent volume for Temporal’s database.

Copilot · 2026-04-17T12:47:11Z

+    healthcheck:
+      test: ["CMD", "tctl", "--address", "localhost:7233", "cluster", "health"]
+      interval: 10s
+      timeout: 5s
+      retries: 10
+      start_period: 30s


postiz-app depends on postiz-temporal being service_healthy, but the Temporal healthcheck runs tctl inside the temporalio/auto-setup container. This is relatively brittle (CLI availability/behavior changes) and differs from existing patterns in the repo (e.g. blueprints/peerdb/docker-compose.yml uses a dedicated temporalio/admin-tools container for tctl). Consider switching to a simpler healthcheck (port/grpc probe) or adding an admin-tools container for CLI-based checks so postiz-app startup doesn't get blocked by a failing healthcheck.

Copilot · 2026-04-17T12:47:12Z

+    restart: always
+    environment:
+      - TEMPORAL_ADDRESS=postiz-temporal:7233
+      - TEMPORAL_CORS_ORIGINS=http://localhost:8080


postiz-temporal-ui sets TEMPORAL_CORS_ORIGINS to http://localhost:8080, which won’t match the actual origin when deployed behind Dokploy (and may break UI/API calls due to CORS). Make this configurable (e.g., derived from ${POSTIZ_HOST} / ${domain}) or relax/remove it if not required for this setup.

Suggested change

- TEMPORAL_CORS_ORIGINS=http://localhost:8080

- TEMPORAL_CORS_ORIGINS=https://${POSTIZ_HOST}

Copilot · 2026-04-17T12:47:12Z

+  postiz-temporal-ui:
+    image: temporalio/ui:2.30.0
+    restart: always
+    environment:
+      - TEMPORAL_ADDRESS=postiz-temporal:7233
+      - TEMPORAL_CORS_ORIGINS=http://localhost:8080


PR description says Temporal Web UI is added for monitoring, but this compose change doesn’t include any Dokploy domain/proxy configuration for postiz-temporal-ui (e.g., no corresponding [[config.domains]] entry in template.toml). As-is, the UI container will run but won’t be reachable via Dokploy without an exposed domain/port mapping.

Copilot · 2026-04-17T12:47:12Z

+      - POSTGRES_USER=${DB_USER}
+      - POSTGRES_PWD=${DB_PASSWORD}
+      - POSTGRES_SEEDS=postiz-temporal-postgres
+      - DYNAMIC_CONFIG_FILE_PATH=config/dynamicconfig/development-sql.yaml


postiz-temporal is using DYNAMIC_CONFIG_FILE_PATH=config/dynamicconfig/development-sql.yaml, which is a dev-oriented dynamic config. For a deployment blueprint, this should typically use the production SQL dynamic config (consistent with e.g. blueprints/peerdb/docker-compose.yml using production-sql.yaml) to avoid enabling dev defaults in production.

Suggested change

- DYNAMIC_CONFIG_FILE_PATH=config/dynamicconfig/development-sql.yaml

- DYNAMIC_CONFIG_FILE_PATH=config/dynamicconfig/production-sql.yaml

greptile-apps · 2026-04-17T12:47:41Z

+      postiz-temporal-postgres:
+        condition: service_healthy
+    healthcheck:
+      test: ["CMD", "tctl", "--address", "localhost:7233", "cluster", "health"]


tctl not present in auto-setup image — healthcheck always fails

tctl is only bundled in the temporalio/admin-tools image, not in temporalio/auto-setup. The official Temporal docs state: "Together with the tctl CLI, these binaries are available in the temporalio/admin-tools Docker image." Running CMD tctl inside the postiz-temporal container will exit with "executable file not found", so the container is never marked healthy, and postiz-app (which requires condition: service_healthy) will never start — defeating the purpose of this fix.

A TCP-reachability check is the most portable alternative since you can't rely on any specific CLI being present in the auto-setup image:

Suggested change

test: ["CMD", "tctl", "--address", "localhost:7233", "cluster", "health"]

test: ["CMD-SHELL", "nc -z localhost 7233 || exit 1"]

If nc is also unavailable, a pure-shell approach works: ["CMD-SHELL", "(echo > /dev/tcp/localhost/7233) 2>/dev/null || exit 1"].

greptile-apps · 2026-04-17T12:47:42Z

+        condition: service_healthy
+
+  postiz-temporal:
+    image: temporalio/auto-setup:1.27.2


temporalio/auto-setup is deprecated

Docker Hub marks this image as: "⚠️ DEPRECATED — This image is no longer maintained and will not receive updates." The recommended replacement is temporalio/server paired with temporalio/admin-tools for schema setup, as shown in the official samples. This is fine for a quick fix, but worth tracking for a follow-up migration.

…fix healthcheck

Copilot

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 3 comments.

Copilot · 2026-04-19T08:44:25Z

+    healthcheck:
+      test: ["CMD-SHELL", "tctl --address localhost:7233 cluster health || exit 1"]
+      interval: 10s
+      timeout: 5s
+      retries: 10


The postiz-temporal healthcheck runs tctl, but this compose file does not include a temporalio/admin-tools sidecar (and in this repo tctl is typically run from that image, e.g. blueprints/peerdb/docker-compose.yml:78-85). If tctl isn’t present in the temporalio/server image, the healthcheck will fail indefinitely and postiz-app (which depends on condition: service_healthy) will never start. Consider switching the healthcheck to a simple port/TCP probe on 7233, or add an admin-tools container and move the tctl-based healthcheck there (and depend on that instead).

Copilot · 2026-04-19T08:44:26Z

+      - DYNAMIC_CONFIG_FILE_PATH=config/dynamicconfig/production-sql.yaml
+    volumes:
+      - postiz-temporal-config:/etc/temporal/config/dynamicconfig


postiz-temporal sets DYNAMIC_CONFIG_FILE_PATH=config/dynamicconfig/production-sql.yaml but mounts a brand-new named volume on /etc/temporal/config/dynamicconfig. Named volumes start empty, so this mount will mask any dynamicconfig files shipped in the image and the referenced production-sql.yaml won’t exist unless you provision it elsewhere. Either remove this volume mount (if you want the image defaults) or provide production-sql.yaml via a Dokploy mount (template.toml [[config.mounts]]) or a bind mount directory like other templates do (see blueprints/peerdb/...).

Copilot · 2026-04-19T08:44:26Z

+  postiz-temporal-ui:
+    image: temporalio/ui:2.30.0
+    restart: always
+    environment:
+      - TEMPORAL_ADDRESS=postiz-temporal:7233
+      - TEMPORAL_CORS_ORIGINS=https://${POSTIZ_HOST}
+    depends_on:
+      postiz-temporal:
+        condition: service_healthy


This PR description says it “adds the Temporal Web UI”, but the template currently doesn’t expose postiz-temporal-ui through Dokploy (no [[config.domains]] entry exists in blueprints/postiz/template.toml). As a result the UI won’t be reachable after deployment unless Dokploy is configured manually. Consider adding a domain mapping for postiz-temporal-ui (e.g., a temporal.${domain} subdomain) or updating the PR description if the UI is intended to remain internal-only.

…rvice

Siumauricio · 2026-07-07T20:31:25Z

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

`postiz`

Deploy: error (110s)
Container states at failure time: postiz-app-1: created · postiz-temporal-ui-1: created · postiz-temporal-1: restarting · postiz-temporal-postgres-1: running · postiz-postgres-1: running · postiz-redis-1: running
Issues:
- the deployment finished with ERROR (see log below)
Deploy log (tail):

Container compose-generate-virtual-bus-fpnqjm-postiz-temporal-1 Error dependency postiz-temporal failed to start
dependency failed to start: container compose-generate-virtual-bus-fpnqjm-postiz-temporal-1 is unhealthy
Error: ❌ Docker command failed
Error occurred ❌, check the logs for details.

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

# Conflicts: # blueprints/postiz/docker-compose.yml

Copilot

Copilot was unable to review this pull request because the user who requested the review is ineligible. To be eligible to request a review, you need a paid Copilot license, or your organization must enable Copilot code review.

Siumauricio · 2026-07-08T06:18:12Z

Closing — superseded by #851 (already merged), which added the full Temporal stack to the Postiz template. Thanks for the contribution!

fix(postiz): Resolve Temporal crash loop by isolating Workflow database

080cd86

Copilot AI review requested due to automatic review settings April 17, 2026 12:43

dosubot Bot added the size:XS This PR changes 0-9 lines, ignoring generated files. label Apr 17, 2026

Copilot started reviewing on behalf of chahat1709 April 17, 2026 12:44 View session

github-actions Bot deployed to Preview April 17, 2026 12:44 View deployment

Copilot AI reviewed Apr 17, 2026

View reviewed changes

greptile-apps Bot reviewed Apr 17, 2026

View reviewed changes

fix(postiz): Address AI review feedback, update healthcheck and configs

a39a5f2

github-actions Bot deployed to Preview April 17, 2026 13:00 View deployment

github-actions Bot deployed to Preview April 19, 2026 08:08 View deployment

fix(postiz): use temporalio/server image, add dynamic config volume, …

3abfbe5

…fix healthcheck

Copilot AI review requested due to automatic review settings April 19, 2026 08:40

Copilot started reviewing on behalf of chahat1709 April 19, 2026 08:40 View session

github-actions Bot deployed to Preview April 19, 2026 08:41 View deployment

Copilot AI reviewed Apr 19, 2026

View reviewed changes

fix(postiz): remove missing dynamic config reference from temporal se…

9430a34

…rvice

github-actions Bot deployed to Preview May 14, 2026 04:57 View deployment

Merge remote-tracking branch 'origin/canary' into fix-postiz-temporal

64e2d72

# Conflicts: # blueprints/postiz/docker-compose.yml

Copilot AI review requested due to automatic review settings July 8, 2026 06:05

Copilot AI reviewed Jul 8, 2026

github-actions Bot deployed to Preview July 8, 2026 06:07 View deployment

Siumauricio closed this Jul 8, 2026

	- TEMPORAL_CORS_ORIGINS=http://localhost:8080
	- TEMPORAL_CORS_ORIGINS=https://${POSTIZ_HOST}

	- DYNAMIC_CONFIG_FILE_PATH=config/dynamicconfig/development-sql.yaml
	- DYNAMIC_CONFIG_FILE_PATH=config/dynamicconfig/production-sql.yaml

	test: ["CMD", "tctl", "--address", "localhost:7233", "cluster", "health"]
	test: ["CMD-SHELL", "nc -z localhost 7233 \|\| exit 1"]

Conversation

chahat1709 commented Apr 17, 2026 • edited by greptile-apps Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Greptile Summary

Confidence Score: 4/5

Uh oh!

github-actions Bot commented Apr 17, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Copilot AI Apr 17, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 17, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 17, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 17, 2026

Choose a reason for hiding this comment

Uh oh!

greptile-apps Bot Apr 17, 2026

Choose a reason for hiding this comment

Uh oh!

greptile-apps Bot Apr 17, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Copilot AI Apr 19, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 19, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 19, 2026

Choose a reason for hiding this comment

Uh oh!

Siumauricio commented Jul 7, 2026

postiz

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Uh oh!

Siumauricio commented Jul 8, 2026

Uh oh!

This branch was successfully deployed

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

chahat1709 commented Apr 17, 2026 •

edited by greptile-apps Bot

Loading

github-actions Bot commented Apr 17, 2026 •

edited

Loading

`postiz`