Still hosting gitlab.

The CI on forgejo is, unfortunately, nowhere near as good.

Given how long gitlab has been struggling to fix basic bugs and instead creeping into features - hello-oo bloated and slow vscode-like web editor and non-ephemeral runner management - I’m not sure they have any staff left to let go. But it’s nice they found an excuse to shed their remaining talent and avoid complete stock devaluation.

The planning is happening openly, including a voluntary separation window.

“We don’t understand how the Dead Sea Effect works, and we want to super-size the damage.”. Okay. Bill.

This should be a note on the sidebar of all ask-* subs.

Wow. I had to stop reading this one. Long on words, poor on writing and spelling and neither circling a theme so much as just edgelording on everything social, I’m not sure whether it was ever getting somewhere.

But life’s too short for 6000 words on The Things That Suck With Stuff I Don’t Use.

I shudder to imagine what they’d think of a car with a clutch and a left-toe switch for the high-beams.

• node.js
• mariadb server
• redis

You’ve got suppy-chain attacks and boutique complexity in three easy steps. Squeeze it into a flatpak or crutch on containers to frustrate validation and it’s the perfect footgun from a security standpoint.

Why be misunderstood from human reading comprehension when we can be misunderstood from sloppy reading comprehension? Yay for technology!

Heh. Container mafia going “hush, don’t worry about iso27002, just one more pull, bro.”

Do the sysctl fix and you’re fine to wait for a patch.

Disable the sandbox bit and it’s bobbitted, right ?

I’d like to host micro-instances for 1-2 subs for software: XYZApp-news and XYZApp-help or so, on the equivalent of a spur or leaf node.

But aPub seems to need M:M comms and so it needs to be out in the world instead of hidden behind an aPub proxy. True?

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.