Postiz Template is missing the temporal service leading to ECONNRESET error

[killshotroxs]

To Reproduce

The current Postiz template in Dokploy appears to be incomplete. It does not include the Temporal service, which is required for Postiz v2+ (Temporal-based architecture).

As a result, deployments created via the Dokploy template fail to start correctly:

postiz_postiz (app) → 0/1
postiz_postiz-postgres → may fail or restart
postiz_temporal → missing entirely or not configured

This leads to:

App not booting (depends on Temporal)
Background jobs not running
In some cases, cascading failures or high CPU usage
Expected Behavior

The Dokploy template should provision all required services, including:

Postiz app (ghcr.io/gitroomhq/postiz-app)
PostgreSQL
Redis
Temporal (temporalio/auto-setup)
Actual Behavior

Temporal is missing from the template, causing incomplete deployment and service instability.

Suggested Fix

Update the Dokploy Postiz template to include a properly configured Temporal service with:

PostgreSQL connection
Correct environment variables
Network linkage with Postiz app

Current vs. Expected behavior

Actual Behavior

Temporal is missing from the template, causing incomplete deployment and service instability.

Suggested Fix

Update the Dokploy Postiz template to include a properly configured Temporal service with:

PostgreSQL connection
Correct environment variables
Network linkage with Postiz app

Provide environment information

I am on Ubuntu 20 VPS
using the dokploy template of postiz which has a latest tag but still has issues.

Which area(s) are affected? (Select all that apply)

Docker Compose

Are you deploying the applications where Dokploy is installed or on a remote server?

Same server where Dokploy is installed

Additional context

No response

Will you send a PR to fix it?

Maybe, need help

[dosubot]

Hi @killshotroxs! I'm Dosu and I’m helping the dokploy team.

You're right — the current Postiz template only includes the app, PostgreSQL, and Redis services, with no Temporal service [1].

There's already an open PR in the templates repo that addresses this: PR Dokploy/dokploy#658 — "fix: update to postiz templates for v2 with temporal". It adds the Temporal workflow engine along with a dual-database architecture (Temporal and Postiz need separate databases). However, it hasn't been merged yet due to some style guide violations that need to be resolved.

If you'd like to help move this forward, contributing to or reviewing that PR would be the fastest path. In the meantime, you could manually add a Temporal service to your compose setup following the blueprint conventions — the key pieces are:

• temporalio/auto-setup image (pinned to a specific version, not latest)
• A dedicated PostgreSQL database for Temporal
• Network connectivity to the Postiz app service
• restart: unless-stopped and proper health checks

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}
   

[dosubot]

You're right — the current Postiz template only includes the app, PostgreSQL, and Redis, with no Temporal service.

There's already an open PR in the templates repo that addresses this: PR #658 — "fix: update to postiz templates for v2 with temporal". It adds the Temporal workflow engine along with a dual-database architecture (Temporal and Postiz need separate databases). However, it hasn't been merged yet due to some style guide violations that need to be resolved.

If you'd like to help move this forward, contributing to or reviewing that PR would be the fastest path. In the meantime, you can manually add a Temporal service to your compose setup. The key pieces are:

• temporalio/auto-setup image (pinned to a specific version, not latest)
• A dedicated PostgreSQL database for Temporal
• Network connectivity to the Postiz app service
• restart: unless-stopped and proper health checks

The template conventions also require using expose instead of ports, no container_name or networks keys, and version 3.8 for the compose file.

To reply, just mention @dosu.

---

Docs are dead. Just use Dosu.