If you use docker, it doesnt matter the distro. And to use docker, you dont really need to understand how/why it works. As long as you can take an example compose file and spin it up (docker compose up) it'll be less complicated in the long run than managing plex on the host machine (or most software for that matter, which is why containerization is so popular.)
rutrum
It seemed nice at first, but one major issue: GPU passthrough was a nightmare. It cant be done in the UI and I didnt understand fully how it worked. There are many different tutorials not by promox that are outdated or may not work. It was frustrating enough I jumped to NixOS. Other hiccups included having to go to the terminal to passthrough drives for openmediavault, but that one was kind of straightforward atleast, and it worked first time.
In hindsight, I didnt actually need to virtualize everything at that level, so I never really had a good use case for it anyway. I use containers over entire VMs.
From my short time with proxmox, I had to dive into the command line to do configuration at the host level that couldnt be done with the UI. I think nixos will help replacd those ad hoc configurations with nix options. In the many articles I read about gpu passthru, and also doing harddrive passthru, I had to work in the host debian environment.
I dumped proxmox because I couldnt get gpu passthrough to work, and havent looked back. Nixos modules and docker have served me better than VMs for my usecase.
I used nixos-mailserver with success, and very little configuration. Most of it was dns, and thr guide walked me through it. You would have to a nixos box somewhere though. I spun one up on my vps for it.
Yes I've got that set but still running into issues at runtime.
It was not configured correctly. Its a nixos bug. Thanks for pointing out the daemon config its what lead me down to solving the docker problem.
Yes thats the nvidia-container-toolkit I described above. It should be installed.
As a community, I do think we get hungup on distros. Most of them, as you mentioned, are just different defaults of the same packages.
But at the maintainer level, I do think theres a lot of work distributions do at making sure the software they choose as defaults are up to date, secure, and work with one another. I dont enounter it often, but relying on maintainers to prevent mismatched depencies ending up in the day-to-day linux user has to be worth something. And every set of defaults needs that level of assurance, I would think. Im not a maintainer, I could be off here.
What database client do you use? Maybe a plain database is enough with the right client.
Doesn't need to. That's a plus though. I think the features I like the most are dropdowns for foreign keys and more specific column types. For instance, a date type gives me a calendar picker, and an image type lets me upload and image and then see it as I browse the data.
I really think the learning curve will be less than you think. Please consider at least reading the installation instructions. Here's the page for linuxserver.io's maintained plex docker container. I've linked to the usage section, where you can copy the compose file to deploy it. https://github.com/linuxserver/docker-plex?tab=readme-ov-file#usage