Web & Data Systems / Built / deployed
Technical Publishing & Portfolio Stack
First-party Flask/PostgreSQL publishing system powering the technical archive, case studies, admin workflow and public portfolio, with a parallel Tor v3 publishing path.
OVERVIEW
What I built.
First-party Flask/PostgreSQL publishing system powering the technical archive, case studies, admin workflow and public portfolio, with a parallel Tor v3 publishing path.
Built the publishing application that powers the technical archive, portfolio, case studies and admin workflows.
Used first-party Flask/Jinja/CSS with PostgreSQL-backed posts and Markdown rendering.
Maintained a separate Tor v3 publishing topology alongside the public clearnet site.
SYSTEM ARCHITECTURE
How the system is divided.
Public web -> edge/ingress -> Flask/Gunicorn -> PostgreSQL.
Tor v3 path -> Tor onion service -> Nginx -> Flask/Gunicorn -> PostgreSQL.
Admin publishing uses authenticated sessions and sanitized Markdown rather than raw HTML storage.
NETWORK / DATA FLOW
What talks to what.
TECHNOLOGY STACK
The technical surface.
IMPLEMENTATION
How it works in practice.
- 01
Public web -> edge/ingress -> Flask/Gunicorn -> PostgreSQL.
- 02
Tor v3 path -> Tor onion service -> Nginx -> Flask/Gunicorn -> PostgreSQL.
- 03
Admin publishing uses authenticated sessions and sanitized Markdown rather than raw HTML storage.
TESTING & VALIDATION
How I know it works.
Public route HTTP checks
Tor stack health/deploy checks
Admin authentication and redirect behavior
Markdown sanitization path
Database backup
Portfolio/project route crawl
EXTERNAL SERVICES & DEPENDENCIES
What sits outside the core.
ENGINEERING EVIDENCE
Artifacts behind the claims.
BOUNDARIES / CONSTRAINTS
What the project does not pretend to solve.
—No third-party analytics/scripts on the public portfolio
—Secrets and onion identity remain outside Git
—Clearnet and onion ingress are separate operational paths
RESULT / CURRENT STATE
What this produced.
A self-hosted publishing and portfolio system that can present deep engineering work and long-form technical notes across public and onion access paths.