Quick update on site status

Author:

We’re making great strides! I finally got https://keel.sh/ and my private container registry to play nice, so I can very quickly deploy stuff from my (Silverblue) workstation with a few quick podman commands. Still trying to find a git + ci/cd solution that doesn’t fucking suck – the consensus seems that gitea is actually the least bloated option. I’m seriously considering just building a lil’ container with sshd and lighttpd and a bigass volume mount and calling that my git server – that’s basically what I did on the old stack, and it was solid. CI/CDing it sounds hellish though; I really want my docker builds running on the server with automatic tagging, and DIND is a mess. Eh, we’ll see. It should still be more ergonomic than Gitea. Seriously, fuck gitea.

swaous.asuscomm.com and tardiggas.org have ssl certs and they’re working nice and shmoove. Once I’ve got swaous.asuscomm.com fully set up, I’mma focus real attention on clarkeis.com. And probably fix the current tardiggas stack because, like, a quick gust of wind could blow this shit down. It’s a container that I installed sshd in and gave a bunch of friends access to. It’s bullshit. I might just bite the damn bullet and use GitHub Actions for this one, because giving a bunch of people ssh access to a git container on my cluster is a really fucking bad idea.

Eventually I need to move the docker registry to its own little cubbyhole at docker.clarkeis.com, but for now it’s on swaous.asuscomm.com. You heard me right. Docker Registry’s api is currently occupying the /v2 path on my main publicfacing domain name. It’s a mess. I honestly don’t know what I was thinking at the time but this works and I don’t want to replicate the black magic (a single secret import, thanks to the simplicity of k3s, but I’m super fucking lazy).

In other news: AnyVM is going nicely and I think I can start PCP proper soon, so by… summer 2025? PCPCMS should be rendering most of my site, because fuck wordpress. And of course I’ve already started planning a custom container orchestrator, but that’s a far future plan if I ever do it. K3s YAML is disgusting but not so disgusting that I need to suspend all development on everything that matters to replace it.

Anyways, that’s how stuff is goin’ down. Expect to see changes as I get fed up with WordPress and work on designing my homepage. Sayonara!