Apps & Control Planes / Built / integrated
Social Publisher
Dedicated publishing engine with scheduler, queue worker, PostgreSQL/Redis state, reproducible source pinning and restore-tested backups; external publishing remains deliberately disarmed until credentials are configured.
OVERVIEW
What I built.
Dedicated publishing engine with scheduler, queue worker, PostgreSQL/Redis state, reproducible source pinning and restore-tested backups; external publishing remains deliberately disarmed until credentials are configured.
Integrated a dedicated publishing runtime around a pinned upstream base rather than embedding social delivery into Content Studio.
Configured scheduler, queue worker, PostgreSQL/Redis state, reproducible builds and backup/restore verification.
Kept external Meta connectivity intentionally disarmed until credentials and dispatch are explicitly enabled.
SYSTEM ARCHITECTURE
How the system is divided.
Approved content -> publisher dispatch boundary -> scheduler/queue worker -> external network adapter.
PostgreSQL and Redis hold durable/queue state.
Backups include database and application storage and are validated with disposable restore tests.
NETWORK / DATA FLOW
What talks to what.
TECHNOLOGY STACK
The technical surface.
IMPLEMENTATION
How it works in practice.
- 01
Approved content -> publisher dispatch boundary -> scheduler/queue worker -> external network adapter.
- 02
PostgreSQL and Redis hold durable/queue state.
- 03
Backups include database and application storage and are validated with disposable restore tests.
TESTING & VALIDATION
How I know it works.
Pinned upstream reproducible build
Container health endpoint
Scheduler/worker runtime check
Database/storage backup
Disposable PostgreSQL restore verification
External dispatch deliberately disabled without credentials
EXTERNAL SERVICES & DEPENDENCIES
What sits outside the core.
ENGINEERING EVIDENCE
Artifacts behind the claims.
BOUNDARIES / CONSTRAINTS
What the project does not pretend to solve.
—Meta credentials currently intentionally blank
—Publishing must remain disarmed until explicitly enabled
—Derived upstream code is not claimed as original
RESULT / CURRENT STATE
What this produced.
A separately operable publishing layer that can be tested safely without accidentally posting to external platforms.