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?

Yum-cron. Daily. Rolling bounce on a schedule.

It has been rock-solid for 20 years, but lennart’s cancer and the growing amount of shite they’re shoveling into EL has caused a few issues here and there with 7, 9 and 10. (Skipped 8 because f that)

But, today, it works. So that’s year 23 and 8 months.

I presumed the draw of us-east-1 was its lower cost

At no time is pub-cloud cheaper than priv-cloud.

The draw is versatility, as change didn’t require spinning up hardware. No one knew how much the data costs would kill the budget, but now they do.

universal single point of failure.

If it’s not a region failure, it’s someone pushing untested slop into the devops pipeline and vaping a network config. So very fired.

I love the “git gud” response. Sacred cashcows?

This looks very nice.

Um, you know you’re supposed to keep dev tools in dev, right? Npm->commit->release payload without npm. Far fewer supply-chain exploits.

Still crutching on containers?

It’s an exciting world of file-to-object-to-file thunking. I’m surprised when it all works.

I block bad writers. It hurts my brain reading their work and I get sad.

No need to look up how to do a clean install.

The suggestion you don’t know that enterprise OSes have been doing clean installs and removals of a product and all its dependencies for 25 years as a critical test before issuing said packages suggests you’re working around too many problems without solving them.

We did devops by pxe-based kickstart and then simple package updates before devops was even a word. It still does better than Ansible does now.

Still container crutches?

Dependency hell is self-inflicted, but sparkle-junkie devs are complicit: it’s their fault they don’t know of long-term-support enterprise OSes and don’t use one as a primary port.

Still on container crutches?