This PR updates and optimizes the Postiz blueprint to ensure full compatibility with Dokploy's architecture and recent Postiz requirements. The main focus is on stabilizing the Temporal integration and fixing issues that were causing deployment failures.
• Temporal Integration Refactor: Updated the Temporal stack (PostgreSQL, Elasticsearch, and Auto-setup) to ensure correct startup order and health check synchronization.
• Social Media API Support: Added environment variable placeholders for major social media platforms (LinkedIn, X, Facebook) to the template.toml for easy configuration via the Dokploy UI.
I have tested the template in my instance, so the maintainers don't spend time trying to figure out what's wrong.
I have added tests that demonstrate that my correction works or that my new feature
🔄 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/851
**Author:** [@berkeguvenc](https://github.com/berkeguvenc)
**Created:** 5/7/2026
**Status:** 🔄 Open
**Base:** `canary` ← **Head:** `canary`
---
### 📝 Commits (1)
- [`357124d`](https://github.com/Dokploy/templates/commit/357124dc7cb6703222daa43e9443fe1e9d6180f7) feat(postiz): update docker-compose and template for Temporal integration
### 📊 Changes
**3 files changed** (+93 additions, -31 deletions)
<details>
<summary>View changed files</summary>
📝 `blueprints/postiz/docker-compose.yml` (+75 -5)
📝 `blueprints/postiz/template.toml` (+18 -8)
📝 `meta.json` (+0 -18)
</details>
### 📄 Description
…tion
## What is this PR about?
This PR updates and optimizes the Postiz blueprint to ensure full compatibility with Dokploy's architecture and recent Postiz requirements. The main focus is on stabilizing the Temporal integration and fixing issues that were causing deployment failures.
• Temporal Integration Refactor: Updated the Temporal stack (PostgreSQL, Elasticsearch, and Auto-setup) to ensure correct startup order and health check synchronization.
• Social Media API Support: Added environment variable placeholders for major social media platforms (LinkedIn, X, Facebook) to the template.toml for easy configuration via the Dokploy UI.
## Checklist
Before submitting this PR, please make sure that:
- [x] I have read the suggestions in the README.md file https://github.com/Dokploy/templates?tab=readme-ov-file#general-requirements-when-creating-a-template
- [x] I have tested the template in my instance, so the maintainers don't spend time trying to figure out what's wrong.
- [x] I have added tests that demonstrate that my correction works or that my new feature
---
<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/851
Author: @berkeguvenc
Created: 5/7/2026
Status: 🔄 Open
Base:
canary← Head:canary📝 Commits (1)
357124dfeat(postiz): update docker-compose and template for Temporal integration📊 Changes
3 files changed (+93 additions, -31 deletions)
View changed files
📝
blueprints/postiz/docker-compose.yml(+75 -5)📝
blueprints/postiz/template.toml(+18 -8)📝
meta.json(+0 -18)📄 Description
…tion
What is this PR about?
This PR updates and optimizes the Postiz blueprint to ensure full compatibility with Dokploy's architecture and recent Postiz requirements. The main focus is on stabilizing the Temporal integration and fixing issues that were causing deployment failures.
• Temporal Integration Refactor: Updated the Temporal stack (PostgreSQL, Elasticsearch, and Auto-setup) to ensure correct startup order and health check synchronization.
• Social Media API Support: Added environment variable placeholders for major social media platforms (LinkedIn, X, Facebook) to the template.toml for easy configuration via the Dokploy UI.
Checklist
Before submitting this PR, please make sure that:
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.