Do you mean being dependent on people having “done it in nix before” so you can copy it? Definitely true to some extent. The language takes a bit of getting used to. Haven’t watched the video so idk context, but if using docker on nix there’s a great tool called compose2nix that converts compose files for docker or podman into declarative nix files. That took a lot of the challenge away for me personally.
Comment on What's on my Home Server 2025 – NixOS Edition - YouTube
LastYearsIrritant@sopuli.xyz 5 weeks ago
Kinda cool how the configs work, but it feels like you need to rely a little too much on having premade configs available for the things you want to do.
hangonasecond@lemmy.world 5 weeks ago
ruffsl@programming.dev 5 weeks ago
I’m not the original author, even with the YouTube title being as is, but what do you mean? Perhaps relying that the desired services exist as nix packages, or that nix packages have desired defaults or exposes desired config parameters?
There are two other nix media server config projects I can think of, but I think this approach mostly facilitates the install, but not the entire initial config setup, given that a lot of the stack’s internal state is captured in databases rather than text config files. So simplifying the backup and restoration of such databases seems the next best thing to persist your stack configs with nix.
xamino@feddit.org 5 weeks ago
A lot of software exposes the general “config” or “environment” object too. Thanks to that I haven’t encountered many things I couldn’t go in my Nix config for already packaged services.
And you can always fall back to Docker in Nix, which has the benefit of all the flexibility and will still declaratively declare your deployments.
So in practice this works out very well in my case, I haven’t had to fight Nix (apart from the initial learning curve).