fix: update to postiz templates for v2 with temporal

[rubixvi]

• Remove deprecated version field for compose file format compliance
• Add Temporal workflow engine with PostgreSQL and Elasticsearch
• Configure comprehensive social media platform integrations (Discord, LinkedIn, X, TikTok, YouTube, etc.)
• Add Cloudflare R2 storage provider configuration options
• Include email service configuration for notifications
• Implement Redis persistence and health checks
• Add proper service networking and dependencies

Temporal and Postiz must be seperated in terms of the databse for it function with the dual database setup.

Greptile Summary

Updated Postiz template to v2 with Temporal workflow engine integration. Added comprehensive social media platform integrations and configuration options for Cloudflare R2 storage and email services.

Key changes:

• Added Temporal workflow engine with dedicated PostgreSQL and Elasticsearch services
• Configured dual-database setup separating Postiz and Temporal databases
• Added social media platform integrations (Discord, LinkedIn, X, TikTok, YouTube, Facebook, etc.)
• Enhanced Redis with persistence configuration and health checks
• Added Cloudflare R2 storage provider options
• Included email service configuration

Issues found:

• Missing required version: "3.8" field (violates AGENTS.md style guide)
• Network definitions added (dokploy-network and temporal-network) which may conflict with Dokploy's network isolation model per style guide
• URL scheme changed from HTTPS to HTTP - verify compatibility with Dokploy's SSL termination

Confidence Score: 2/5

• This PR has critical style guide violations that must be fixed before merging
• Score reflects a critical syntax violation (missing version field required by style guide) and network configuration that conflicts with Dokploy conventions. The functional changes appear sound (dual database setup for Temporal separation, comprehensive platform integrations), but the implementation violates documented standards that could cause deployment or isolation issues
• Pay close attention to blueprints/postiz/docker-compose.yml - must add version field and reconsider network definitions

_{Last reviewed commit: 21ca847}

Context used:

• Context from dashboard - AGENTS.md (source)

[github-actions]

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Name	Status	Preview	Last Commit
templates	✅ Ready (View Log)	Visit Preview	21ca847

[rubixvi]

@Siumauricio , just so you're aware, I know there's an inclusion of networks, but this is required for the two postgres database to function without conflict.

[Copilot]

Pull request overview

This pull request updates the Postiz template to version 2 with Temporal workflow engine integration. The changes add comprehensive social media platform integrations, email and cloud storage configurations, and separate database infrastructure for Temporal.

Changes:

• Remove deprecated version field from docker-compose.yml for v3.8 compliance
• Add Temporal workflow engine with dedicated PostgreSQL database and Elasticsearch
• Configure environment variables for 15+ social media platforms (Discord, LinkedIn, X, TikTok, YouTube, etc.)
• Add Cloudflare R2 storage and email service configuration options
• Implement Redis persistence with health checks and explicit networking configuration

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 13 comments.

File	Description
blueprints/postiz/docker-compose.yml	Adds Temporal services (workflow engine, PostgreSQL, Elasticsearch) with dedicated networking; configures Redis persistence; adds environment variables for social integrations
blueprints/postiz/template.toml	Defines environment variables for email, Cloudflare R2 storage, and social media platform API credentials

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 6 comments.

[SimonSchroffner]

Hi, just wanted to check when this will be done. The current template does not work anymore.

[Siumauricio]

@Siumauricio , just so you're aware, I know there's an inclusion of networks, but this is required for the two postgres database to function without conflict.

Why do we need this?

[Siumauricio]

@greptile review

[greptile-apps]

_{2 files reviewed, 3 comments}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

missing version: "3.8" field - the style guide (AGENTS.md:149) requires Version: MUST be 3.8

Suggested change

	services:
	version: "3.8"
	services:

Context Used: Context from dashboard - AGENTS.md (source)

_{Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!}

[greptile-apps]

defining networks violates the style guide (AGENTS.md:150) which states: "NEVER include: ports (use expose only), container_name, networks (Dokploy handles isolation)"

while some existing templates use dokploy-network for cross-service communication, the separate temporal-network may cause issues with Dokploy's network isolation model

Context Used: Context from dashboard - AGENTS.md (source)

[greptile-apps]

changed URL scheme from https:// to http:// - verify this works correctly with Dokploy's reverse proxy and SSL termination

[rubixvi]

@Siumauricio , just so you're aware, I know there's an inclusion of networks, but this is required for the two postgres database to function without conflict.

Why do we need this?

Cause the two postgres will end up conflicting with each other. Postiz has one and Temporal has another. And temporal is very demanding compared, logically you can merge the postgres but it'll just degrade performance.