stik.wtf

The workspace — it’s called Metis now — needs a teacher: the big always-on model that plans and reviews for the smaller ones.

The homelab page now carries the workstation’s full BIOS profile — the V/F curve offsets, the boost table, the power limits, and the memory timings that take a DDR5-6400 kit to 7000 MT/s.

Approving a whitelist application used to end with me typing a command into a console.

A 1.5B model on its own container, answering questions about this site.

Every page footer reads live wattage off the node’s CPU packages and memory controllers, plus my workstation’s CPU and both GPUs, and keeps a running kWh total.

It’s called own metal, and it’s for people who serve their site from hardware they control and self-host at least one other thing — git, mail, chat, a game server, whatever.

Forgejo now runs in its own container on the node, pushing mirrors out to GitHub.

The server’s whitelist has a real front door now: a form that asks the questions worth asking and emails me a link to approve or turn down.

Stole the best idea I’ve seen on someone else’s site: a 64x64 board anyone can paint, one pixel every thirty seconds.

This site now serves itself from its own container on the node, through its own tunnel.

The storefront now runs fully self-hosted in its own container on the node, with Stripe handling payments instead of Shopify taking its cut.

Two merges in one morning: this site is now a 512KB Club green-team member (22KB uncompressed, with everything on) and indexed in Kagi’s Small Web.

Cable-management night escalated into a storage upgrade: a 1TB SSD joined the node, and this site already lives on it.

Planned the whole site this morning, started building it this afternoon.

Fabric + Geyser now run in their own container on the Proxmox node. play.stik.wtf survived the move.