Hi there! I see you have discovered PostFlowX. This deploy repo is the "storage" which explains the whole project and has the whole plan in it. Feel free to scroll through the files and look at the plan that was created by me while talking like 5h to AI. Please read the disclaimer before you judge me about using AI realtalk. Btw if you checked the PostApi-PrePostFlowX Repo: Thats the little project, which this project was born out of.
A self-hosted social publishing platform. One installation = one Docker Compose stack: web (frontend + own BFF), server (several cooperating processes) and db (PostgreSQL). Integrations such as Instagram are plugins: separate programs started and supervised by the server, built in their own repos and managed from the web UI.
Plan: first the infrastructure (Infra v0.1, verified with a demo plugin), then the Instagram plugin.
web ──(only to the Gateway)──► server container ──(only the Gateway)──► db (PostgreSQL)
server container
Controller (PID 1) starts everything, assigns rights, restarts crashed processes
├─ Watchdog health checks (through the Gateway)
├─ IPC Gateway the only door; every message between processes passes here; only DB client
├─ Executioner runs plugins as sub-processes, checks their rights, asks the admin for untrusted ones
│ └─ plugins (Instagram, TikTok, Reddit …) talk only to the Executioner
├─ Plugin-Mgmt stores plugin packages on disk
└─ File-System stores files (images, JSON, …) on disk
Start here → docs/ROADMAP.md (work top to bottom, Step 0 → 15, then the Instagram plugin).
| File | Content |
|---|---|
docs/ROADMAP.md |
the path, with checkpoints and "done when" per step |
docs/FEATURES.md |
product summary + all features with priority and step |
docs/ARCHITECTURE.md |
containers, processes, sockets, identity, flows, data |
docs/CONTRACTS.md |
IPC rules + plugin spec (messages live in proto/) |
docs/DECISIONS.md |
all decisions, fixed defaults, open points, verified checks |
docs/SECURITY.md |
threats, targets, must-pass tests |
Repos: postflowx-deploy (this one: Compose, docs, proto/) · postflowx-server (controller, watchdog, gateway, executioner, plugin-manager, filesystem, sdk/, plugins/demo/) · postflowx-web · later postflowx-plugin-instagram.
bash scripts/init-secrets.sh # DB password, master key, internal CA + certs into ./secrets (git-ignored)
cp .env.example .env
docker compose up --build # needs sibling checkouts ../postflowx-server and ../postflowx-webStatus: planning done, no application code yet.
I know I know. I used AI to plan this whole project. That's because I need to get that shit done while I have the time and resources for it. The code I am going to write inside this whole project will not be generated by AI. I promise that because I hate AI to code. I want to understand it myself. I only use AI to yea like plan this whole thing and to get an idea how to start, what do I want to implement and what the important things are to look at. I am doing this since this is my first ever really big project and additionally I am a rather weak one man army.
If you have any tips or want to contact me to idk help me coding, planning or even contribute to it then PLEASE DO SO REALLY. I will be thankful for any help out here.
I am a solo (noob) dev that is trying to improve his skills while being jobless (basically waiting for next year to apply for universities and maybe do work & travel). Yea I guess that's all you need to know for now. If you try to contact me look at my profile, add me on discord _entro_ or shoot me an email at alexhuber1811@posteo.com