A big part of it is the open source aspect, yes.
In addition, Plex is increasingly weighing down their offering with new “features” of questionable value. Some would probably use the term “enshittification” to describe the trend over the past year or two.
I bought a plex lifetime license a long time ago (2013), but for a newcomer I would recommend Jellyfin. You can also run them both simultaneously with no issue and decide for yourself.
Thanks for the heads up.
I plan on using digital ocean’s Spaces (s3-alike) where possible and also it’s intended to be a personal instance, at least to start - just for me to federate with others and subscribe to my communities. Given that, do you think it’ll still use much disk (block device) storage?
Might be time to familiarize myself with DO’s disk pricing…
A 13-year-old former gaming computer, with 30TB storage in raid6 that runs *arrs, sabnzbd, and plex. Everything managed by k3s except plex.
Also, 3-node digital ocean k8s cluster which runs services that don’t need direct access to the 30TB of storage, such as: grocy, jackett, nextcloud, a SOLID server, and soon a lemmy instance :)
Oh no you forgot kubernetes!
You could get notified with a PR to update a version with renovate.
(Assuming you have your selfhosting configurations checked into source control, which I realize as I’m typing this that it might not be the norm…)
Ubuntu LTS and k3s for all workloads (except for plex, which I’ve not gotten around to migrating yet…)
I run k8s, mostly because I use it for work and really enjoy the gitops approach to management. Previously I used docker compose.
Damn, why not use k8s at that point
I can understand avoiding Docker, Inc software, but not an aversion to containers. Why do you prefer baremetal over containerization?
Neat, never heard of this one and I’m not sure that I need it in my ecosystem, but I’ll probably set it up anyway since my *arrs like having friends
For the 2nd point, see https://docs.docker.com/config/containers/resource_constraints/#limit-a-containers-access-to-memory