02 / Full stack / Operations
Production Media Platform
A full-stack media platform with accounts, content workflows, personalization, search, subscriptions, and production deployment safeguards.
A complete product. And the systems that keep it standing.
Relationships behind the interface.
Users → Content → Creators → Playlists → Activity → Subscriptions. Simplified explanatory diagram, not a product screenshot.01 / The problem
The interface is only one part of a production platform. Accounts, relational data, content workflows, and releases all need to work together without putting user data at unnecessary risk.
02 / What I built
I designed and implemented the frontend, backend APIs, database models, authentication, user systems, and administration features, then built the infrastructure to deploy and operate the application.
03 / Engineering decisions
Model the relationships, not just the pages.
Relational models connect users, media, creators, tags, playlists, watch history, subscriptions, likes, comments, and personalized activity.
Make releases a recoverable operation.
Automated releases include rollback protection, database migration safety checks, backups, and runtime verification.
Own the whole path to production.
Next.js, React, TypeScript, Prisma, and SQLite form the application stack; Bun, Caddy, and Cloudflare support the production setup.
Production in context
registered users
monthly unique visitors
Figures supplied in my CV. These are reported production snapshots, not live telemetry or an independent audit.
04 / Inspect the engineering
Here’s what
you can open.
Related public deployment reference, not the media platform source. The product is anonymized here; audience figures come from my CV.
safe-sqlite-deployWhat the public reference demonstrates
- A Python CLI that validates a candidate against a consistent SQLite copy and checks previous-runtime read/write compatibility.
- Verified backups, restricted migrations, revision-specific health checks, and runtime rollback that leaves live database writes intact.
A standalone single-host reference. Activation includes downtime; it is not a zero-downtime orchestrator and does not automatically restore an old database.
The repository README describes its scope and limitations. Production claims and public reference-code behavior are intentionally kept separate.