What you are installing
PostQueen ships as one container image. Inside it a small proxy sits in front of three Node processes, so from the outside there is only ever one port to think about. Next to her she needs three services: a PostgreSQL database, Redis, and Temporal, which is the scheduler that actually fires your posts at the right minute. The official Docker Compose file starts all of that for you, which is why it is the path we recommend to almost everyone. You do not have to install PostgreSQL, Redis or Temporal by hand.Which path is for you
I just want to see it
Docker Compose on your own machine. Around five minutes, nothing permanent, delete it
afterwards with one command.
I want to run it for real
Docker Compose on a small server, on your own domain, with HTTPS. Start here if other
people will use it.
I want to change the code
Run her from source with hot reload, so you can edit the frontend or add a provider.
I already run Kubernetes
A Helm chart, for people who already have a cluster and know they want one.
What those other options in the sidebar mean
The sidebar lists a few more install methods. You almost certainly do not need them, but here is what each one is, so you can stop wondering.What she needs to run
A small virtual machine is enough. Two vCPUs and 2 GB of RAM will run a single-person install, and 4 GB is more comfortable once a few people share it. The full numbers, including disk and the outbound addresses she needs to reach, are on System Requirements. You will also need Docker. Both install guides walk you through getting it.One thing worth knowing before you start. PostQueen marks her login cookies as secure,
which means a real install needs HTTPS. Locally that is handled for you. On a server you
put a reverse proxy in front of her, and
Domain and HTTPS explains what that means and does it
with you step by step.