I also try to shove everything into Fedora in some fashion, and things don't always fit in cleanly, and usually there are no guides for doing weird stuff on Fedora, but for me it's been an easier and more interesting maintenance burden. Also sometimes I want to do weird stuff that bespoke distros don't seem easily able to accommodate. I did shoehorn Fedora into the role of VPN gateway, such that it only had routes out to my chosen VPN endpoints, and would NAT traffic behind it out on the VPN. It works reliably for me, and I enjoyed learning the details of putting it together, but it's certainly not for most people. I had to sit and spend some time understanding nftables.
I used to consider Fedora DOA for hobbyist hosting, but with the changing times and loss of CentOS it has been the lowest friction move for me so far. I'm trying to deploy most stuff in clouds anyways, and with the more nimble/disposable deployments in the cloud with opentofu it feels much less of a downside to me that a Fedora release support term is 18mo, I have probably already re-deployed that service as part of regular maintenance over a year, or I should have. It's also been an easy platform for simple container hosting using podman and quadlets, and so there is much less exposure to changes in Fedora OS, I can just re-roll the container host with updated packages and not really care about it.
It has made me think I should look more into CoreOS for personal use, but since things Just Work now, and I don't expect knowing CoreOS will specifically land me a sweet job, I haven't quite gotten there yet.
Not to harp on the cloud shit too hard, but something I have also really liked is per container service I roll out, each gets its own storage volumes as needed, separate from the disposable OS drive, and each can have its own backup strategy in AWS. Notifications are configurable. If you watch your data budget and backup policies, backup and storage for regular services can be really cheap. BUT, I understand you are probably looking at media storage, and at those volumes AWS will absolutely ream us heh.
Lastly, I think these topics are a good portrait of how storage can be very complicated, and why it's so expensive in enterprise. Once you need more reliability than going down to buy a consumer retail disk, the cost skyrockets. I remember trying to figure out a few years ago what the sweet spot for drive size was, to minimize failure chance, and exposure and potential raid rebuild times (eg, if you have a raid1 of two 12TB disks, and one fails, what is the chance the lone good source doesn't choke in the 13 or so hours @ 250MB/sec it takes to bring the raid back optimal?)... and how many disks I should be using in a raid array to minimize those outages. I think I read backblaze has something like 50% of the disks in their raid arrays are redundant.. in other words, in a 10 disk array, 5 hotspares. We're not even talking about backups yet.