

On an average day, I spend 0 minutes managing the homelab.
0 is the goal. Well done !
Edit: Ha! Some masochist down-voted that.


On an average day, I spend 0 minutes managing the homelab.
0 is the goal. Well done !
Edit: Ha! Some masochist down-voted that.


How it started : 0
Max : 0
Now : 0
Iso27002 and provenance validation goes brrrrr


You’re not alone.
The industry itself has become pointlessly layered like some origami hell. As a former OS security guy I can say it’s not in a good state with all the supply-chain risks.
At the same time, many ‘help’ articles are karma-farming ‘splogs’ of low quality and/or just slop that they’re not really useful. When something’s missing, it feels to our imposter syndrome like it’s a skills issue.
Simplify your life. Ditch and avoid anything with containers or bizarre architectures that feels too intricate. Decide what you need and run those on really reliable options. Auto patching is your friend (but choose a distro and package format where it’s atomic and rolls back easily).
You don’t need to come home only to work. This is supposed to be FUN for some of us. Don’t chase the Joneses, but just do what you want.
Once you’ve simplified, get in the habit of going outside. You’ll feel a lot better about it.


Still crutching on containers?
Comically, the organization with the worst history for virtualization now doubled-down on SAAS. This is certainly going well.


Still crutching on containers?
They reversed that policy
For now.
Careful with the ugreen: I found if you get the cheaper option, you can’t hot-swap a disk anymore. They don’t make that really clear.


Got a version without docker?


Container crutches. Ew. And if a dev can’t spell self-hosted, then I don’t trust them to do it properly.


Canada would be happy to receive many of these skilled refugees. There are programmes now for medical workers, and if global companies prefer American timezones for worker surveillance, then have I got news for them !
Where’s the Bazel people at?
CI compatible to GitHub actions
Ugh. More yaml?
It’s still yaml shit though.


Packer builds the terraformable/openTofuable templates to launch into the hypervisor where chef (eventually mgmtConfig) will manage them from there until they die.
All that is launched by git. Fire and forget. Updates are cronned.
There are no containers. Don’t got time to fuck about. If Systemd wasn’t an absolute embarrassment I’d not worry about updates even as much as I do, which isn’t much aside from the aforementioned cancer.
Like, what 8 letters are abbreviated between those two Ns? Are we supposed to know?


I see it’s running Ansible. That’s an obvious risk.


So a guy reads from an outline or script into a YouTube clip we can view (after ads) with a transcript we can then summarize with an LLM so we can replicate the outline or script originally used?
The downvote and next buttons are, like, right there.


You mean we can charge our cars without risking damage or wear-and-tear to the port? What will this do to the planned obsolescence of the port if we don’t beat it up every day? Will it be pristine like my phone port next to the goddamned headphone jack?
Is there a text summary?