What Postiz needs
In this lesson I look at what a self-hosted PostEase needs. Before I start anything, PostEase is an open source social media scheduler. You write a post once, choose the networks and PostEase publishes it at the time you set. When you host it yourself, your accounts, drafts and keys stay on your own machine. Before you start you need Docker with the Compose plugin and about 4GB of memory free for containers. On a Mac Kolima provides both. Install Kolima, Docker and Docker Compose with Homebrew, then run Kolima start with 4 CPUs, that is a processor cores and 8GB of memory. These three commands check that Docker answers. Docker 29 and Compose 5. The virtual machine behind Docker has 4 CPUs and almost 12 GB of memory. Other projects run there too, so this stack has to stay small. I start from a small starter repository called Busses Omelab. It is a Git repository and it holds everything except the secrets. a compose file, a make file with short commands, two small settings files and two scripts. The compose file describes the seven services, these are their names. The first three are Postiz itself. The Postiz container holds the web application, the API, which is the application programming interface, web pages call and the workers that publish posts, PostgreSQL stores, users, posts and connected accounts. Redis keeps short-lived data such as caches. The other four are Temporal. A scheduled post is a promise about the future published at 9 on Tuesday and try again if the network is down. Temporal is a workflow engine that keeps such promises in its own database so a timer survives a restart, it needs its own PostgreSQL Elasticsearch to search its workflows and it comes with a web interface. Elasticsearch is a java program and by default it takes a large share of the memory it can see. One line caps its heap at 256 megabytes. With that cap the whole stack uses about two and half gigabytes of memory and the Posties container is most of it. Next the network, I look for every published port. Only two services publish a port, Posties on 4.7 and the Temporal Web Interface on 8.7, both are bound to 1.7.0.1, the loopback address so only programs on this Mac can connect. Without that address, Docker publishes the port on every network interface and anyone on your network could open the signup page. Then versions, the images come from a separate file. Every image has an exact version. Postis is pinned to 2.25.2, one release behind the newest, on purpose. In the lesson about upgrades I move it to 2.25.3, the way you will upgrade your own instance. the passwords? they are not in the compose file each one is a variable like this the colon and the question mark make compose a stop with an error when the variable is empty so nothing can start with a blank password the values come from a secrets file outside the repository which the command make prepare generates that is the whole design seven containers in about two and half gigabytes, two ports on the loopback address, pinned versions and secrets kept out of git.