A production Django platform and personal infrastructure lab used to practice secure ingress, reverse-proxy design, containerization, storage and operational automation—without exposing private network details.
DjangoDockerNGINXCloudflareGunicornTrueNAS
01 / EVIDENCE TRACE
Follow each claim through the system.
ARCHITECTURE.MAPSelect any component to inspect it.
The cyan connection shows where the selected evidence enters the system.
→
→
→
→
INSPECTINGApplication
Containerized application processes run behind the proxy with production settings.
Connected to selected evidence
02 / ENGINEERING DECISIONS
Why the architecture looks this way.
01
No direct port exposure
A managed tunnel keeps inbound access narrow and avoids publishing the private network.
02
One clear ingress boundary
TLS and routing responsibilities stay legible at the edge and reverse proxy.
03
Infrastructure as a learning system
Real operations make reliability, upgrade and recovery tradeoffs concrete.
CLAIM.BOUNDARY
Credibility includes saying what the work does not prove.
Architecture is intentionally presented without IP addresses, storage inventory, private hostnames or household infrastructure details.