Container crutches. Ew.

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.

The writing in this article is absolutely terrible. It needs some serious clean-up before the message isn’t impaired by the medium.

I go to pixelfed to post my art and view other peoples art. that’s it. I don’t go there to read posts or what’s going on in peoples lives.

Yes but being able to do that is a design goal of the fediverse

Is it? Beause that seems really dumb.

Here’s a radical idea: sometimes, web services are built with features you don’t use. Sometimes you don’t even *value *those features. But, in cases where your preference isn’t in the majority, the decision to include those features won’t match your personal preference.

Sometimes, the ability to share and see content between different sites is even a core value.

Weird.

For more information, search “false consensus”.

You may want to learn how you can configure your own accounts on various services to manage what you see on each one. Because, to some extent, that’s a configuration option.

The installation workflow begs for supply-chain exploits. Given this and its oob install, it probably breaks iso27002 as well.

I’ll wait. NextCloud and OwnCloud both have 27002-compliant installs (the latter needs some review), so I need to stick with those.

Still container-dependent?

This. If I pay the cost in frustration and anguish and soul-searching and demanding justice from an uncaring god, I want some thing for it. I want documentation. I want my lessons learned from the post incident review. I want something I can hack into mgmtConfig to make sure nothing else will do that too.

Struggling for no payoff is the absolute worst thing.

What you get is something with an acceptable warranty and maybe some support.

What you then realize is what you DON’T have on your consumer gear.

I just checked out frigate, and I see it crutches on docker. Anything docker-free?

You found a solution and you are looking for a problem.

This is not the way it goes. You identify a problem, and if the solution involves self-hosting then you solve it with self-hosting.

They don’t realize the colors are arbitrary. Many don’t realize the internet spans the world.

Socialism and democracy are good words in some countries. Socialism is how my sister in law gets to retire at 55 and in excellent health, and democracy is how they got that.

I dearly wish to use and support this app.

But here’s the thing: containers - like so many other mechanisms - suffer from supply-chain risks due to reduced validation to the degree assumed and required compared to, say, good packaging that integrates with the resident source of truth on a given system. Containers, like so many other risky mechanisms that dates back to CPAN or earlier, cannot exist in a secure environment.

For those of us working where we can to minimize repair/recovery work through best practice, Immich cannot be run.

I know there’s a homebrew workaround, but given it’s external to the dev effort it’s a risk that it won’t suddenly work as a reliable update resource; and that risk stymies uptake for us.

Now, I know I’ve suggested there’s imperfection in a number of favourite technologies and methods, and that’s fine. If downvotes is how you defend these sacred cows, I understand.

Correct: it’s like trying to equate “correct” with “popular”, and keeping in mind how the last US elections have turned out.

But it’s good to be in a big network of other users with the same product, nonetheless.

Anything docker-free?

Still crutching on containers?