Just the ones we will quit.

Snipe-it failed iso27002 when I last checked.

1. Avoid anything with bad supply chains that fail iso27002
2. Yum via cron
3. Huh. That’s all of it.

27001

docker

Heh.

Day job: oneScrote and fucking ansible

Night job: some wiki for the architecture, but just config management for the config detail : we run the docs and it’s done. Thankfully not fucking ansible; because in any environment where there are options, it’s not fucking ansible.

Ansible using SSH

The moment you discover anything else, you’re gonna be so pleased. It’ll seem so modern! So fast!

Check out gatus.

It doesn’t do SNMP. That’s … bold.

Iso27002 says I can’t run this.

Please also consider mikrotik brand gear. I’ve been told they’re especially easy to manage as one moves from manual control to something declarative like terraform(opentofu).

The CI turned me off though. It’s like they saw how bad GitHub is for CI and said “no notes. Just like that”

And I use the CI config a huge amount.

there are complete ansible-repos

Ansible is toxic. Anything else?

For sure. And their bumbling has made it harder to deactivate all the useless bloat and get the good web-editor back. And a host of other mind-numbingly short-sighted decisions that show they’re fully run by LostBoy coders who were never mentored and just don’t know better.

But tuning can come after. And their CI is way fucking better than forgejo’s facepalm of a GitHub clone. And that’s a thin reason, but, yeah.

It’s monstrous, but gitlab installs from one big RPM on a base box; and with one config file you’re up.

most of the world have Android

Heck, most of the Known Universe. This is how I say it to my fanboy sibling who moves those goalposts just so only America is in-frame and the numbers show a small advantage for the Home Team.

It’s called the universal operating system for a reason.

If they call themselves that, it really doesn’t count. It’s like how trump ended like 10 wars to get his FIFA peace medal.

two containers

Good luck, but I’m out.

What’s the big deal? For 20 years in the enterprise space it’s been yum upgrade -y && reboot into cron and no issues. At the day job I even had satellite (5 and that shitball 6) cronned up to do my promotion automatically (even when 6 had shit for scheduling and I had to cron-parallel-xargs a better one). All cron.

Hell, I barely pay attention to the email reports now. It’s been that long. Okay, prod updates on Friday night only; but that’s our only nod to risk. Because even after the metastatic fatberg that is Systemd, it’s still barely reliable.

What’s the added risk for Debian packages? Imperfect replacement? No signed manifest to compare against? What?

USEnet would like a word.

1. Self-hosting guide appears missing
2. Other guides have crazy writing errors
3. Setup looks convoluted.

What I’ve seen makes me bet I could be dragging iso27002 out and marking all the rules it breaks. …and the devs won’t know what that means.

Yeah. It sucks that the protocol works and everyone can use it. It’s the worst.