Something funny happened a little while ago: I read about Fresh RSS, it sounded nice, and I installed it on a server and started using it. That would not have happened a year ago, but then again, a year ago I didn't have any NixOS servers.
For the past few years, my RSS feeds have lived locally on my phone only. The idea behind that was sound, since I can mostly take time to read when I'm away from my computer anyway, but it never quite worked in practice. Many things are easier to read on a larger screen, and it was brittle to trust a phone app to manage the read/unread status of thousands of articles across a hundred feeds. When I switched phones, I could migrate the feeds, but the read/unread status was lost along the way.
What I really wanted was a server-side feed aggregator, software that runs on a server, manages RSS feeds, and can be read through a web interface or client applications. I had wanted that for a while, but never took the step because it would be yet another side project to maintain. Now, with some NixOS experience, adding a working Fresh RSS configuration, including backups, took 9 lines of Nix code plus a dozen more for the nginx reverse proxy. That installation has run hands-off for months, and if the server breaks, a new one running the exact same configuration can be spun up in about 15 minutes.
By contrast, installing Fresh RSS outside NixOS means extracting archives, configuring permissions, installing and configuring nginx and php-fpm, setting up Let's Encrypt certificates, configuring backups, and hoping you remember all of it when reinstalling later. Container images shorten the process somewhat, but they still leave steps to remember and do not guarantee the same result months later.
The author dislikes maintaining side projects, even small ones, because emergency maintenance and hours of upgrade work drain the desire to work with computers. Reproducible configuration is what makes self-hosting feel manageable.
Source: Hacker News · Summarized by HeadlinesBriefing