Looks like one of the 2cellos folks but not 100% sure ( https://youtube.com/@2celloslive )

But couldn’t find the video from the screenshot.

You got a lot of relevant answers so I want to point out something else:

You’re hosting your own services. By yourself. Fuck everyone with a broom who tries to gatekeep that. And I don’t mean wooden side first.

Seriously, your question is on point here from my perspective and as long as it has a connection to running services by your own I personally would love more diversity in hosting solutions.

Personally, I’d love to see people share more about their provider agnostic opentofu deployment or someone who went all in on AWS lambdas for weird stuff.

Oh that’s an approach I haven’t even considered, I es always very … Black and white :D

Thanks for the inspiration, should I find a bucket of time in the future I’ll give it a shot!

Not the person you asked but for me:

It’s because they’re a documentation mess caught in a release/stable discussion that I don’t understand.

Perhaps that changed in the last year, haven’t looked into them again since then - but unless there’s a trigger (new server setup or official release for example) I simply don’t have the time and energy to invest.

And check for each music service their offered music. I’ve checked out tidal actually today with one of those export playlist tools and about 10% of my (honestly: niche) music wasn’t available.

No one forces unattended updates. And containerd is already living in the userspace.

If every dev would live on a kernel level stability approach we’d will not have a containerd release at all.

One thing that was only mentioned briefly by someone else is the physical button turning on the computer.

Similar to the paperclip test figure out where the power button goes into the mainboardw and bridge that with a short cable. Is possible that by moving the case the old button lost a cable.

This is just one more thing to test though, it’s really trial and error as you know :)

From what I understand: CasaOS is simply an abstraction layer and takes away a lot of the manual work.

I agree with you that this shows down learning quite a bit.

I see three ways forward for you:

a) switch to a Linux base system, Debian, arch, nixos, whatever resonates and set up everything from scratch. High learning curve but no more hidden things.

b) same as a but as a separate setup. This is what I would recommend if you have the time and cash. Replicate what’s already working and compare.

c) figure out how to do things manually within the CasaOS framework. Can’t help you there though :)