Workshop notes, build logs, reverse engineering, and other rabbit holes.
Describe a host as one block of YAML, run one playbook, get a configured server - and the same playbook does it to a whole fleet, the same way every time. The inventory says what a host should be; the AWX job log says …
A 6-node K3s cluster as one git repo. Push to master, ArgoCD picks it up, nothing gets deployed by hand. Three layers, sync waves, and the parts that took longest to get right.
Host public services from a residential line without the home IP ever landing in DNS. A 5 EUR VPS, a WireGuard tunnel, and three OPNsense NAT rules.
Klipper on a Pi Zero 2W hidden inside the printer base, powered and serial-fed from the stock display header. Plus direct-drive, dual Z, custom heatbreaks, and the mods that followed once the host was clean.
I learned FreeCAD 1.x by drawing parts for hobby rockets: nosecones, fin sections, motor mounts, recovery bays. The channel that taught me the workflow, and the parametric discipline that stuck around for everything …
I forked okalachev/flix, printed a frame, and learned the IMU pipeline the slow way. Here is what every step between 'motor spins' and 'thing hovers' actually costs.