NixOS is making me less afraid

The author describes moving from a phone-only RSS workflow to running FreshRSS on a server and how NixOS turned that into a low-friction experiment rather than a daunting side project. Previously feeds lived on a phone and read/unread state was brittle across devices; a server-side aggregator was desirable but seemed like an installation and maintenance burden. With NixOS the FreshRSS deployment (including backups) fit into nine lines of Nix plus about a dozen lines for the nginx reverse proxy; the proxy required rewriting cookie paths for a location-specific proxy_pass, a personal complication. The result has run hands-off for months and can be recreated on a new machine in roughly fifteen minutes, so there is no reason not to try new software.

That contrasts with the traditional FreshRSS route: extract archives, set permissions, install nginx and php-fpm, configure pools and TLS, set up backups, and memorize the process for future reinstalls. Using the project’s container image trades some steps for others (Apache+mod_php inside the image and TLS left to the host) but still leaves reproducibility problems because container builds diverge over time. After unsuccessful attempts with CFEngine, Ansible, podman and k3s and brittle shell scripts, the author finds NixOS configurations act like executable, repeatable instructions that actually reduce maintenance anxiety and make experimentation practical.