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.

Explore architecture

STATUSBuilt / deployed

AREAWeb & Data Systems

STACK6 documented technologies

INTEGRATIONS4 connected / bounded services

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.

Architecture boundary

Public web -> edge/ingress -> Flask/Gunicorn -> PostgreSQL.

Architecture boundary

Tor v3 path -> Tor onion service -> Nginx -> Flask/Gunicorn -> PostgreSQL.

Architecture boundary

Admin publishing uses authenticated sessions and sanitized Markdown rather than raw HTML storage.

NETWORK / DATA FLOW

What talks to what.

TRACE PATHFocus or tap a stage to trace the flow from source to that point.

01Reader / admin

→data / control

02Public edge or Tor v3

→data / control

03Nginx / Caddy path

→data / control

04Flask + Gunicorn

→data / control

05PostgreSQL

→data / control

06Rendered portfolio / articles

TECHNOLOGY STACK

The technical surface.

01Flask

02PostgreSQL

03Gunicorn

04Nginx

05Tor

06Markdown

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.

TEST 01

Public route HTTP checks

TEST 02

Tor stack health/deploy checks

TEST 03

Admin authentication and redirect behavior

TEST 04

Markdown sanitization path

TEST 05

Database backup

TEST 06

Portfolio/project route crawl

EXTERNAL SERVICES & DEPENDENCIES

What sits outside the core.

CORETechnical Publishing & Portfolio Stack

↔Cloudflare edge/tunnel

↔Tor v3 Onion Service

↔PostgreSQL

↔Nginx / Gunicorn

ENGINEERING EVIDENCE

Artifacts behind the claims.

01NOTELive reazromen.com

02NOTEPortfolio pages

03NOTETechnical archive

04NOTEAdmin publishing UI

05NOTEPostgreSQL schema

06NOTETor v3 deployment

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.