Kushan

Absolutely! Here’s my CI pipeline, it’s actually super basic: https://gist.github.com/neoKushan/bd92031bb9c8db3320e8c19d5dae3194

Happy to answer questions if you like.

I just added my compose files to the repo, that CI file and set up renovate https://github.com/renovatebot/renovate to create my PR’s for me.

I generally agree with the sentiment but don’t pull by latest, or at the very least don’t expect every new version to work without issue.

Most projects are very well behaved as you say but they still need to upgrade major versions now and again that contains breaking charges.

I spebt an afternoon putting my compose files into git, setting up a simple CI pipeline and use renovate to automatically create PR’s when things update. Now all my services are pinned to specific versions and when there’s an update, I get a PR to make the change along with a nice change log telling me what’s actually changed.

It’s a little more effort but things don’t suddenly break any more. Highly recommend this approach.

Of course he’s quadrupling down and he’ll keep on doubling down again and again because that’s the only way he stays out of prison and it’s the only way MAGA doesn’t collapse, so everyone around him will continue to back him.

The only way this will end is if he dies or a bunch of folks finally use the second amendment right they’ve been so precious about that they let hundreds of school kids die each year for.

What a fucking disgrace.

In your compose file, make sure you’ve added runtime: nvidia.

You also don’t need to deploy the resources and reserve the GPU, you can remove the entire deploy section when using the nvidia runtime.

I just changed my compose reference to update the volume and base image. Worked a treat.

Jellyfin is a fork of emby (from when it went closed source), so that makes sense. They have diverged quite a bit but seems the Auth hasn’t changed enough.

I think that’s actually quite sensible, our lawyer wasn’t flagging some clear cut legal certainty, he was flagging risk.

Risk can be mitigated, even if the chance of it panning out is slim.

I work for a large enterprise firm, our corporate lawyer has told be about this exact scenario so I’m inclined to believe it’s real.

That being said, for established projects it won’t be that hard to prove the non-AI bit because you have a long commit history that predates the tooling.

Even if you were to assume that all commits after a certain date were AI generated, the OP is slightly off in their attestation that any AI code suddenly makes the whole thing public domain, it would only be if a majority of the codebase was AI coded (and provably so).

So yes all the vibe coded shite is a lost cause, but stuff like Windows isn’t in any danger.

I don’t understand the backlash against using an MIT/Apache licence at all. Those licenses are far more permissive than GPL but completely compatible.

The only downside is that someone could fork the code and close source it, but the original code still remains available and that’s where the community will stay.

I’m running a TrueNAS build which has just grown in time. Started off at 5x8TB drives, then added 5x16TB drives and just last week added another 5x26TB drives (that was costly ☠️). It’s all running in a very cheap case using an old threadripper machine I had (2950x), which thankfully supports ECC (128GB purchased years ago before the sillyness).

It’s about the storage I have in my server right now - using 15 drives ☠️

Start off simple, use something like uptime-kuma just to check your services are available - takes minutes to set up and can send you notifications when something goes down. It can plug into docker directly to check if a container is up, as well as perform HTTP checks that the service is responding, plus some other cool stuff.

(Side note, I set up ntfy to handle notifications and it’s great! Another solid recommendation but you can use discord web hooks or whatever as well)

The other options described here are good for gathering and visualising data, but it takes quite a bit to set them up and even more to configure the right kinds of alerts to notify you when something is wrong. A simple “is this docker container running” check or a “does this respond with a http 200” check gets you like 95% the way there.