#homelab
7 posts
-
Putting three old projects back online with one Dockerfile
A roguelike, a pathfinding visualiser and FairSight, all Streamlit apps, now on my homelab under one deployment pattern. Plus a bug that only exists once a game is public.
-
My "LAN speed test" was actually an internet speed test
I'd just replaced a faulty LAN cable, so when iperf3 said 30 Mbit/s I blamed the new one. The traffic had never touched the LAN.
-
My new monitoring paged me twice on day one. Good.
A flaky HTTP/2 ping and a backup job that ran fine by hand but not under systemd. Both were real bugs, and both got caught.
-
Getting a homelab ready to run for three months without me
No sleep, a watchdog, key-only SSH, a wiped HDD turned into storage and backups, a second way in, and an outside alarm for when the box goes dark.
-
Auditing a gaming laptop that thinks it's a server
A read-only audit of my homelab box. No firewall, password SSH, no backups, and 86 unsafe shutdowns on the SSD.
-
ShipDoc, part 2: moving off AWS before the account expired
The hackathon's AWS account ended on 18 October. ShipDoc moved to my homelab behind Caddy and a Cloudflare Tunnel, and the old domain now explains where it went.
-
How an old gaming laptop became my homelab
A Lenovo Legion Y540, Arch Linux, SSH and Tailscale. How my "learn Linux" machine turned into the server that hosts my projects.