GAMEHUB /LEARN
Build log &field notes
A Futuristic Gaming Platform Built with AWS & DevOps. Every phase of this project is documented as an honest learning note — what was built, why that choice beat the alternative, the bugs found along the way, and the interview questions it unlocks. Read it online, or download the whole thing as a PDF.
GameHub
[](https://github.com/cijostany6-bit/GameHub/actions/workflows/ci.yml)
OPEN DOCUMENT → STEP 0Step 0 — Reproducible Local Foundation ✅ (2026-10-18)
The stack went from **not runnable at all** (dead AWS RDS endpoint, no local
OPEN DOCUMENT → STEP 1Step 1 — Automated Tests + GitHub Actions CI ✅ (2026-10-18)
a fresh clone with Docker off still gets green unit tests, and the console
OPEN DOCUMENT → STEP 2Step 2 — Game-y UI: Live Background + Self-Hosted Arcade Fonts ✅ (2026-10-18)
served.** Root cause: `Last-Modified: Sep 16` on the old file gave the
OPEN DOCUMENT → STEP 3Step 3 — Real Playable Games ✅ (2026-10-19)
**Every one of the 12 catalogue entries now opens an actual, playable game.**
OPEN DOCUMENT → STEP 4Step 4 — Real Auth + Live on AWS ✅ (2026-10-19)
Players now sign up and sign in before they reach the games, and the whole thing
OPEN DOCUMENT → STEP 5Step 5 — Observability ✅ (2026-10-19)
A deployment you cannot see is a deployment you cannot run. This step makes the
OPEN DOCUMENT → STEP 6Step 6 — Local Kubernetes (kind) + Argo CD ✅ (2026-10-19)
The Compose stack answers "can you run this?"; this step answers "can you run it
OPEN DOCUMENT → STEP 7Step 7 — Security hardening & GDPR ✅ (2026-10-19)
Security is not a feature you add at the end; it is a set of claims that are
OPEN DOCUMENT → STEP 8Step 8 — /learn Documentation Site + PDF Export ✅ (2026-10-19)
The step notes in `docs/` and the `README.md` used to live only as Markdown in
OPEN DOCUMENT → DOCArchitecture decisions (ADRs)
Every non-obvious choice in this project, in the same shape: **context**,
OPEN DOCUMENT → DOCLoad test — what a single t3.micro actually does ✅ (2026-10-19)
A load test is only useful if it is honest about what it measured. This one was
OPEN DOCUMENT → DOCRunbook — GameHub (prod)
export AWS_REGION=eu-central-1
OPEN DOCUMENT → DOCService level objectives — GameHub
Two things are intentionally **not** SLOs:
OPEN DOCUMENT →One command rebuilds all of this
The pages you are reading are generated from the Markdown in the repository — no static-site framework, no npm packages, no network. Running the script again reproduces them byte for byte, and the same content becomes a printable A4 guide.
| Command | What it does |
|---|---|
node scripts/build-learn.js | Regenerate this site and the print guide |
./scripts/build-pdf.sh | Rebuild everything and render learn/gamehub-guide.pdf |