realitaetsverlust

Yuri’s revenge isn’t even close to being mediocre tho, it was an amazing addon for an already amazing game.

Congrats to all the execs, you’ve completely ruined the tech industry.

No - I think they made it (involuntary) better by forcing people into looking into self hosting everything and taking control over their own infrastructure.

No

Steam Deck verified is like 90% done towards linux support

It’s not really about working harder. Before, it just wasn’t a justifiable expense investing time into ensuring proton support or even linux support because a sub 1% OS just isn’t “worth” supporting from a financial standpoint. That changed with the steamdeck and because the steamdeck is actually just a small PC with built-in controller, things that profit the deck also profit the linux ecosystem.

Honestly the steam deck was a genius move from valve.

Terraform and Puppet. Not very simple to get into, but extremely powerful and reliable.

How do you notify yourself about the status of a container?

I usually notice if a container or application is down because that usually results in something in my house not working. Sounds stupid, but I’m not hosting a hyper available cluster at home.

Is there a “quick” way to know if a container has healthcheck as a feature.

Check the documentation

Does healthcheck feature simply depend on the developer of each app, or the person building the container?

If the developer adds a healthcheck feature, you should use that. If there is none, you can always build one yourself. If it’s a web app, a simple HTTP request does the trick, just validate the returned HTML - if the status code is 200 and the output contains a certain string, it seems to be up. If it’s not a web app, like a database, a simple SELECT 1 on the database could tell you if it’s reachable or not.

Is it better to simply monitor the http(s) request to each service? (I believe this in my case would make Caddy a single point of failure for this kind of monitor).

If you only run a bunch of web services that you use on demand, monitoring the HTTP requests to each service is more than enough. Caddy being a single point of failure is not a problem because your caddy being dead still results in the service being unusable. And you will immediately know if caddy died or the service behind it because the error message looks different. If the upstream is dead, caddy returns a 502, if caddy is dead, you’ll get a “Connection timed out”

I can assure you, you will never need them.

I got a USB stick with ventoy installed, got a gparted and an arch linux iso on that thing, I do use those regularly.

Even the oldest, sickest pet will still make an effort to keep themselves alive however they can: eating, drinking water, moving out of the way of danger, etc.

That’s wrong. Especially old cats are very prone to just not eat when they’re old and sick.