Postiz on Coolify

This fork deploys Postiz and its private PostgreSQL, Redis, Temporal, and Elasticsearch dependencies as one isolated Coolify Docker Compose application.

Coolify settings

Setting	Value
Repository	https://github.com/ulpi-io/postiz-docker-compose
Branch	main
Build Pack	Docker Compose
Base Directory	/
Compose Location	/docker-compose.yaml

Copy .env.example into Coolify's environment-variable editor. Replace every replace-me value with a URL-safe secret generated by openssl rand -hex 32.

Alternatively, generate the complete Coolify-ready environment block with fresh secrets:

./generate-env.sh

On macOS, copy it directly to the clipboard:

./generate-env.sh | pbcopy

Only public endpoint

Create an A record for post.con.fyi pointing to the Coolify server. Configure only this domain:

Service	Coolify domain value	Public URL
postiz	https://post.con.fyi:5000	https://post.con.fyi

Leave PostgreSQL, Redis, Temporal, Elasticsearch, Spotlight, Temporal UI, and Temporal admin tools without domains. The Compose file publishes no host ports and defines no custom network; Coolify's proxy is the only public entry point on ports 80 and 443.

The production Temporal service uses the dynamic configuration bundled in its image. Do not add a repository-relative dynamic-config bind mount here: Coolify can materialize that mount as an empty directory and hide the bundled configuration, causing Temporal to crash-loop.

First deployment

1. Set all required environment variables.
2. Keep DISABLE_REGISTRATION=false for the first deployment.
3. Deploy and wait for PostgreSQL, Redis, Elasticsearch, Temporal, and Postiz health checks.
4. Create the first Postiz account.
5. Set DISABLE_REGISTRATION=true and redeploy.

Postiz uploads are stored in the postiz-uploads named volume and served through the same Postiz URL. Database, Redis, Temporal, and Elasticsearch data also use named volumes.

Configure off-server backups before treating the deployment as production.

Optional tools

Spotlight is under the debug Compose profile. Temporal UI and admin tools are under the tools profile. Coolify does not start them during the normal production deployment.

Updating

The Postiz image tracks ghcr.io/gitroomhq/postiz-app:latest. Review the Postiz migration documentation, back up persistent volumes, and then redeploy through Coolify.