Every tutorial tells you to build a portfolio, and almost all of them mean the same thing: one static page with your name, a photo, and a list of projects.
I wanted the portfolio to *be* the project - so this site is a full platform instead. Games, developer tools, a book club, real auth, a real database, deployed on my own domain.
You learn only by building.
The crux
- Five boxes, not one. Frontend (Next.js), backend (FastAPI), Postgres, Redis, and a reverse proxy in front. The proxy is the box beginners skip and the one that makes it feel like a product - Nginx is the receptionist for web traffic: everything knocks on port 80, and it decides whether the request goes to the frontend or to
/api. - Docker is the answer to "it works on my machine". You describe the environment once and that same description runs on your laptop and on the server.
- The app was the easy part. Getting it *reachable* meant learning EC2, ports, security groups, DNS and Cloudflare - a whole evening of vocabulary I had been happily ignoring.
- Three bugs ate that evening: a security group that never allowed port 80 (the app was fine, the door was locked), a 502 because my Nginx config said
localhostinstead of the Docker service name, and a duplicate DNS record sending half my traffic to a dead IP. - Ship before it's finished. The version people can actually visit teaches you more than the one you're still polishing.
The Medium version is the real walkthrough - the architecture reasoning, the networking explained properly, the deployment sequence step by step, and the configs that finally worked.