793eece Add postiz-temporal service to docfix(postiz): add missing Temporal service required by Postiz v2+ker-compose
420aff3 Update temporal image version in fix(postiz): complete temporal service fix with pinned versiondocker-compose
d45d957 Merge remote-tracking branch 'origin/canary' into chahat1709/canary
📊 Changes
1 file changed (+38 additions, -4 deletions)
View changed files
📝blueprints/postiz/docker-compose.yml (+38 -4)
📄 Description
What is this PR about?
Fixes#772
The Postiz template was missing the temporalio/auto-setup service which is required for Postiz v2+. Without Temporal, the app fails to boot and throws ECONNRESET errors.
Changes
Added postiz-temporal service using temporalio/auto-setup:latest
Configured Temporal with proper PostgreSQL connection
Added TEMPORAL_URL and TEMPORAL_WORKER_URL env vars to the app service
Updated depends_on in postiz-app to wait for Temporal to be healthy
Checklist
I have read the suggestions in the README.md file
- [x] I have tested the template in my instance
Greptile Summary
This PR adds the missing postiz-temporal service (using temporalio/auto-setup) and the required TEMPORAL_URL / TEMPORAL_WORKER_URL environment variables to fix Postiz v2+ boot failures. The approach is correct in intent, but has two issues that need resolving before merge.
The postiz-uploads volume is declared twice in the volumes block (lines 82–83), which is invalid and will cause docker compose up to fail.
temporalio/auto-setup is officially deprecated by Temporal (no further updates or security patches); the recommended replacement is temporalio/server + temporalio/admin-tools.
Confidence Score: 3/5
Not safe to merge — duplicate volume key breaks deployment and the Temporal image is officially deprecated.
Two P1 findings: a duplicate volume declaration that prevents docker compose up from succeeding, and reliance on a deprecated image that will never receive security or compatibility updates. Both should be addressed before merging.
blueprints/postiz/docker-compose.yml — duplicate volume and deprecated image
🔄 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/784
**Author:** [@chahat1709](https://github.com/chahat1709)
**Created:** 4/12/2026
**Status:** ❌ Closed
**Base:** `canary` ← **Head:** `canary`
---
### 📝 Commits (3)
- [`793eece`](https://github.com/Dokploy/templates/commit/793eece4075ad5de03a1ab76b377501f13646859) Add postiz-temporal service to docfix(postiz): add missing Temporal service required by Postiz v2+ker-compose
- [`420aff3`](https://github.com/Dokploy/templates/commit/420aff3bf7cf01d7a24f408c56aac1aaff297541) Update temporal image version in fix(postiz): complete temporal service fix with pinned versiondocker-compose
- [`d45d957`](https://github.com/Dokploy/templates/commit/d45d95780c3e9433422a5d4d634b850e59d31664) Merge remote-tracking branch 'origin/canary' into chahat1709/canary
### 📊 Changes
**1 file changed** (+38 additions, -4 deletions)
<details>
<summary>View changed files</summary>
📝 `blueprints/postiz/docker-compose.yml` (+38 -4)
</details>
### 📄 Description
## What is this PR about?
Fixes #772
The Postiz template was missing the `temporalio/auto-setup` service which is **required** for Postiz v2+. Without Temporal, the app fails to boot and throws `ECONNRESET` errors.
## Changes
- Added `postiz-temporal` service using `temporalio/auto-setup:latest`
- - Configured Temporal with proper PostgreSQL connection
- - Added `TEMPORAL_URL` and `TEMPORAL_WORKER_URL` env vars to the app service
- - Updated `depends_on` in `postiz-app` to wait for Temporal to be healthy
## Checklist
- [x] I have read the suggestions in the README.md file
- [ ] - [x] I have tested the template in my instance
- [ ]
<!-- greptile_comment -->
<h3>Greptile Summary</h3>
This PR adds the missing `postiz-temporal` service (using `temporalio/auto-setup`) and the required `TEMPORAL_URL` / `TEMPORAL_WORKER_URL` environment variables to fix Postiz v2+ boot failures. The approach is correct in intent, but has two issues that need resolving before merge.
- The `postiz-uploads` volume is declared **twice** in the `volumes` block (lines 82–83), which is invalid and will cause `docker compose up` to fail.
- `temporalio/auto-setup` is **officially deprecated** by Temporal (no further updates or security patches); the recommended replacement is `temporalio/server` + `temporalio/admin-tools`.
<h3>Confidence Score: 3/5</h3>
Not safe to merge — duplicate volume key breaks deployment and the Temporal image is officially deprecated.
Two P1 findings: a duplicate volume declaration that prevents docker compose up from succeeding, and reliance on a deprecated image that will never receive security or compatibility updates. Both should be addressed before merging.
blueprints/postiz/docker-compose.yml — duplicate volume and deprecated image
<sub>Reviews (1): Last reviewed commit: ["Add postiz-temporal service to docfix(po..."](https://github.com/dokploy/templates/commit/793eece4075ad5de03a1ab76b377501f13646859) | [Re-trigger Greptile](https://app.greptile.com/api/retrigger?id=28130361)</sub>
> Greptile also left **3 inline comments** on this PR.
<sub>(2/5) Greptile learns from your feedback when you react with thumbs up/down!</sub>
**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>
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/784
Author: @chahat1709
Created: 4/12/2026
Status: ❌ Closed
Base:
canary← Head:canary📝 Commits (3)
793eeceAdd postiz-temporal service to docfix(postiz): add missing Temporal service required by Postiz v2+ker-compose420aff3Update temporal image version in fix(postiz): complete temporal service fix with pinned versiondocker-composed45d957Merge remote-tracking branch 'origin/canary' into chahat1709/canary📊 Changes
1 file changed (+38 additions, -4 deletions)
View changed files
📝
blueprints/postiz/docker-compose.yml(+38 -4)📄 Description
What is this PR about?
Fixes #772
The Postiz template was missing the
temporalio/auto-setupservice which is required for Postiz v2+. Without Temporal, the app fails to boot and throwsECONNRESETerrors.Changes
postiz-temporalservice usingtemporalio/auto-setup:latestTEMPORAL_URLandTEMPORAL_WORKER_URLenv vars to the app servicedepends_oninpostiz-appto wait for Temporal to be healthyChecklist
Greptile Summary
This PR adds the missing
postiz-temporalservice (usingtemporalio/auto-setup) and the requiredTEMPORAL_URL/TEMPORAL_WORKER_URLenvironment variables to fix Postiz v2+ boot failures. The approach is correct in intent, but has two issues that need resolving before merge.postiz-uploadsvolume is declared twice in thevolumesblock (lines 82–83), which is invalid and will causedocker compose upto fail.temporalio/auto-setupis officially deprecated by Temporal (no further updates or security patches); the recommended replacement istemporalio/server+temporalio/admin-tools.Confidence Score: 3/5
Not safe to merge — duplicate volume key breaks deployment and the Temporal image is officially deprecated.
Two P1 findings: a duplicate volume declaration that prevents docker compose up from succeeding, and reliance on a deprecated image that will never receive security or compatibility updates. Both should be addressed before merging.
blueprints/postiz/docker-compose.yml — duplicate volume and deprecated image
Reviews (1): Last reviewed commit: "Add postiz-temporal service to docfix(po..." | Re-trigger Greptile
(2/5) Greptile learns from your feedback when you react with thumbs up/down!
Context used:
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.