I think that’s kind of what they meant. I’ve also selfhosted Nextcloud for years, but I only use file sync and calendar/contacts.

Lately I’ve been feeling that Nextcloud is too big and clunky for just that. Like it’s something I’d love to setup at work or for an org, but that it “feels” to heavy for home use these days.

I need to check out Radicale, I think.

OpenSUSE MicroOS or Fedora CoreOS. If you’ll be using containers you’ll have a great time. If you don’t want to deal with transactional systems, then there is literally nothing I’d rather use than Debian.

A day of sorrow indeed… No, joking aside. I gather most people use double click anyway, so this is a good change for that reason. I’ve never really understood it myself (the primary function of the left click being “select” when everywhere else it’s “open” or “go to this thing”?? Alien stuff).

I’m just glad KDE listens to it’s users and adapts to them. Looking forward to the release!

I haven’t used Jellyfin with docker before, just with podman and as a pod in k3s. Both work great and are easy to maintain. If you’re more familiar with podman then docker, then I’d recommend using podman.

openSUSE Tumbleweed or MicroOS. I’ve since long given up on so called “stable release” distros, because a boon to me is to feel like I’m not using software from the stone age, which is what I feel every time I have to use a RHEL, SLE or Ubuntu system.

I’ve used Tumbleweed on laptop and desktop for about 6 years. Never has anything crashed, or at least nothing has ever become unbootable. The most damage ever done by an update was a regression in mesa that made 3d accelerated content absurdly slow, but even that was fixed within a few days.

I use MicroOS on almost all my servers and it’s rock solid.

zypper is slower than pacman, apt and dnf, but it’s extremely usable and easy to work with, even in enterprise scenarios. I’d say it’s basically on par with dnf, usability wise.

openSUSE in general feels extremely stable, and I just love that they went btrfs by default a few years back and just seem to have this future proofing aspect.

Just make sure to mount your volumes with the :z or :Z flags. I have disabled SELinux on servers in the past, but never when I’ve just used podman containers, since “it just works” with SELinux. Literally never had any problems with containers and SELinux.

I’m currently running Jellyfin on a VM in Proxmox and have been for a long time, it works great. My storage solution isn’t glorious, but it is simple. I just have a Debian LXC container in proxmox that bind mounts a large disk and exposes that through an NFS share. Then I’ve installed jellyfin with Podman/Docker on a VM that has that NFS share mounted.

Also, a lot of people have already said this, but Podman/Docker only looks intimidating before you use it. It’s A LOT easier to get applications running then using the “traditional way”. The only thing that could potentially increase complexity for you is to expose a GPU to the docker container. But since you said you don’t have a dedicated GPU I’d strongly recommend using a docker container for the job. Once you’ve used it, you’ll never look back.

I used to manage the file hierarchy myself, but I haven’t done that for years at this point. Same goes for tagging files and such. I just download everything to a root folder called “music” and let lidarr handle everything from there.

Lidarrs default file structure is something like {Artist}/{Album}{Year}/{Track} . This can of course be changed. Then I let lidarr just tag everything for me automatically, embedding album art and such.

It’s a great setup overall, but I don’t know where Lidarr indexes it’s music library from, because some artists and albums might be missing sometimes. That’s really the only pain point.