Portainer Templates logo

Portainer Templates

Postiz Postiz

Stack

Social

An alternative to: Buffer.com, Hypefury, Twitter Hunter, etc...Postiz offers everything you need to manage your social media posts,build an audience, capture leads, and grow your business.

Configuration

Type
Compose
Platform
linux
Source
Repo

Template by xneo1·Source

Services

postiz

Configuration

Image
ghcr.io/gitroomhq/postiz-app:latest
Ports
5000:5000
Volumes
/config/ : postiz-config/uploads/ : postiz-uploads
Env vars
MAIN_URL=https://postiz.your-server.comFRONTEND_URL=https://postiz.your-server.comNEXT_PUBLIC_BACKEND_URL=https://postiz.your-server.com/apiJWT_SECRET=random string that is unique to every install - just type random characters here!DATABASE_URL=postgresql://postiz-user:postiz-password@postiz-postgres:5432/postiz-db-localREDIS_URL=redis://postiz-redis:6379BACKEND_INTERNAL_URL=http://localhost:3000IS_GENERAL=trueDISABLE_REGISTRATION=falseSTORAGE_PROVIDER=localUPLOAD_DIRECTORY=/uploadsNEXT_PUBLIC_UPLOAD_DIRECTORY=/uploads
Restart
always

Image details

User: gitroomhq

postiz-postgres

Configuration

Image
postgres:17-alpine
Volumes
/var/lib/postgresql/data : postgres-volume
Env vars
POSTGRES_PASSWORD=postiz-passwordPOSTGRES_USER=postiz-userPOSTGRES_DB=postiz-db-local
Restart
always

Image details

Pulls: 11.2B
User: stackbrew
Created: Jun 05, 2014
Updated: 38 minutes ago
Status: active

postiz-redis

Configuration

Image
redis:7.2
Volumes
/data : postiz-redis-data
Restart
always

Image details

Pulls: 11.1B
User: stackbrew
Created: Jun 05, 2014
Updated: 9 days ago
Status: active

Standalone Install

Select an install method, to see config/commands for deploying Postiz

Installation method

Install on Portainer

Import all app templates into your Portainer instance, for easy 1-click deploys

  1. Ensure both Docker and Portainer are installed, and up-to-date
  2. Log into your Portainer web UI
  3. Under Settings → App Templates, paste the below URL
  4. Head to Home → App Templates, and the list of apps will show up
  5. Select Postiz, fill in any config options, and hit Deploy

Template Import URL

https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me demo
Original stackfile

The compose file this template deploys, straight from its repo:

services:
  postiz:
    image: ghcr.io/gitroomhq/postiz-app:latest
    container_name: postiz
    restart: always
    environment:
      # You must change these. Replace `postiz.your-server.com` with your DNS name - this needs to be exactly the URL you're accessing Postiz on.
      MAIN_URL: "https://postiz.your-server.com"
      FRONTEND_URL: "https://postiz.your-server.com"
      NEXT_PUBLIC_BACKEND_URL: "https://postiz.your-server.com/api"
      JWT_SECRET: "random string that is unique to every install - just type random characters here!"
 
      # These defaults are probably fine, but if you change your user/password, update it in the
      # postiz-postgres or postiz-redis services below.
      DATABASE_URL: "postgresql://postiz-user:postiz-password@postiz-postgres:5432/postiz-db-local"
      REDIS_URL: "redis://postiz-redis:6379"
      BACKEND_INTERNAL_URL: "http://localhost:3000"
      IS_GENERAL: "true" # Required for self-hosting.
      DISABLE_REGISTRATION: "false" # Only allow single registration, then disable signup
      # The container images are pre-configured to use /uploads for file storage.
      # You probably should not change this unless you have a really good reason!
      STORAGE_PROVIDER: "local"
      UPLOAD_DIRECTORY: "/uploads"
      NEXT_PUBLIC_UPLOAD_DIRECTORY: "/uploads"
    volumes:
      - postiz-config:/config/
      - postiz-uploads:/uploads/
    ports:
      - 5000:5000
    networks:
      - postiz-network
    depends_on:
      postiz-postgres:
        condition: service_healthy
      postiz-redis:
        condition: service_healthy
 
  postiz-postgres:
    image: postgres:17-alpine
    container_name: postiz-postgres
    restart: always
    environment:
      POSTGRES_PASSWORD: postiz-password
      POSTGRES_USER: postiz-user
      POSTGRES_DB: postiz-db-local
    volumes:
      - postgres-volume:/var/lib/postgresql/data
    networks:
      - postiz-network
    healthcheck:
      test: pg_isready -U postiz-user -d postiz-db-local
      interval: 10s
      timeout: 3s
      retries: 3
  postiz-redis:
    image: redis:7.2
    container_name: postiz-redis
    restart: always
    healthcheck:
      test: redis-cli ping
      interval: 10s
      timeout: 3s
      retries: 3
    volumes:
      - postiz-redis-data:/data
    networks:
      - postiz-network
 
 
volumes:
  postgres-volume:
    external: false
 
  postiz-redis-data:
    external: false
 
  postiz-config:
    external: false
 
  postiz-uploads:
    external: false
 
networks:
  postiz-network:
    external: false

Or deploy it directly from the source:

git clone https://github.com/xneo1/portainer_templates
cd portainer_templates
docker compose -f Template/Stack/postiz.yml up -d

More install options in our documentation.

Container Documentation

postiz-postgres Documentation

The PostgreSQL object-relational database system provides reliability and data integrity.

postiz-redis Documentation

Redis is the world’s fastest data platform for caching, vector search, and NoSQL databases.

Serve Postiz on your own domain behind Caddy, Nginx or Traefik. Fill in your domain and copy the result. It's a starting point, some apps need their own base URL or extra headers set too.

Proxying postiz.example.com to http://postiz:5000

Add this to your Caddyfile

postiz.example.com {
	reverse_proxy http://postiz:5000
}

Check the logs first

Nine times out of ten the logs tell you exactly what went wrong.

  • In Portainer, go to Containers, click the container, then Logs. Or run docker logs <container>
  • Exit codes help too: 137 means killed, usually out of memory. 126 or 127 means the command inside the image is broken.

Port already in use

If deployment fails with "Bind for 0.0.0.0:5000 failed: port is already allocated", something else on your server is using that port.

  • Find what's using it: sudo ss -tlnp | grep :5000
  • Stop the other service, or pick a different host port. In 5000:5000 only the left number is yours to change, the right one belongs to the app.

Running but the page won't load

The container is up but nothing appears in your browser.

  • Use your server's real IP: http://your-server-ip:5000. The 0.0.0.0 link Portainer shows isn't a real address.
  • Give it a minute after first deploy, Postiz can take a while to initialise.
  • Make sure your firewall allows the port, e.g. sudo ufw allow 5000

Image won't pull

Test the pull directly on the host: docker pull ghcr.io/gitroomhq/postiz-app:latest

  • "manifest unknown" means the tag no longer exists. This template uses latest, so try pinning a specific version instead.
  • "toomanyrequests" is the Docker Hub rate limit. Log in with docker login to raise it.
  • "no space left on device" means a full disk. Reclaim space with docker system prune

"exec format error"

This means the image was built for a different CPU architecture than your server.

  • Check yours with uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.

Container keeps restarting

The always restart policy relaunches the app after every crash, so the real error can scroll past.

  • Check the logs right after a restart, the last few lines before it died are the useful ones.
  • Get the exit code with docker inspect <container> --format '{{.State.ExitCode}}'
  • Still stuck? Redeploy once with the restart policy set to no so the failure stays visible.

Stack won't deploy

Compose stacks fail fast on small mistakes, and Portainer shows the reason just above the editor.

  • YAML only accepts spaces for indentation, a single tab breaks the whole file.

Raise an issue

Found something which isn't working as it should? Here's how to report it.

A Compose stack

Postiz is a Compose stack, a set of containers (3 of them) defined in one file and brought up together by Portainer, then started and stopped as a single app.

The services

This stack is built from 3 containers that run side by side. Here's each one, with the image it runs and anything it waits for first:

  • postiz runs ghcr.io/gitroomhq/postiz-app:latest, starts after postiz-postgres, postiz-redis
  • postiz-postgres runs postgres:17-alpine
  • postiz-redis runs redis:7.2

Ports

A port is the door the app answers on. A mapping like 5000:5000 means it's reachable on port 5000 of your server, where the left number is yours to change and the right one belongs to the app. It opens:

  • 5000:5000

Volumes

A volume is where Postiz keeps its files so they survive an update or a restart. Without one, anything it saves would sit inside the container and vanish the moment it's recreated. This template mounts:

  • /config/ kept in the postiz-config volume Docker manages
  • /uploads/ kept in the postiz-uploads volume Docker manages
  • /var/lib/postgresql/data kept in the postgres-volume volume Docker manages
  • /data kept in the postiz-redis-data volume Docker manages

Environment variables

Environment variables are the settings you hand over when you deploy, things like a password or a timezone. Postiz takes 15 of them, all with defaults you can leave alone or tweak:

  • MAIN_URL, defaults to https://postiz.your-server.com
  • FRONTEND_URL, defaults to https://postiz.your-server.com
  • NEXT_PUBLIC_BACKEND_URL, defaults to https://postiz.your-server.com/api
  • JWT_SECRET, defaults to random string that is unique to every install - just type random characters here!
  • DATABASE_URL, defaults to postgresql://postiz-user:postiz-password@postiz-postgres:5432/postiz-db-local
  • REDIS_URL, defaults to redis://postiz-redis:6379
  • BACKEND_INTERNAL_URL, defaults to http://localhost:3000
  • IS_GENERAL, defaults to true
  • DISABLE_REGISTRATION, defaults to false
  • STORAGE_PROVIDER, defaults to local
  • UPLOAD_DIRECTORY, defaults to /uploads
  • NEXT_PUBLIC_UPLOAD_DIRECTORY, defaults to /uploads
  • POSTGRES_PASSWORD, defaults to postiz-password
  • POSTGRES_USER, defaults to postiz-user
  • POSTGRES_DB, defaults to postiz-db-local

Restart policy

The restart policy here is always, so Docker brings Postiz back up after a crash and again when the server reboots. Good for anything you want running around the clock. You can change this on the deploy screen. The choices are no (never restart), on-failure (only after a crash), unless-stopped (restart unless you stop it), and always (bring it back no matter what).

Networking

Portainer puts these services on one shared private network, so they can find each other by name (like postiz) while only the ports above are open to you.

Platform

The platform is linux, the kind of system the container is built to run on. Docker and Portainer handle this on a normal Linux server.

Portainer app templates

Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set Postiz up. Add the template list to Portainer once, then deploying Postiz is a click rather than a wall of config.