me and fedora have been boxing for a while now and I’m thinking I want to try something else after I finish designing my next home server case for it.
I’m considering NASty https://github.com/nasty-project/nasty as it’s doing pretty much everything out of box I want to do with this next one already, and even though it’s young, it’s build on nixOS, which I consider mature at this point.
But I have no experience with nixOS. It sounds like it’s a less obnoxious form of fedora coreOS. Any opinions?


No experience with NASty, but:
Had a server die on me about a year ago and wanted more Infra as Code. Tried Fedora CoreOS first, but the cycle was constantly creating a new USB bootable, it was just a bad fit for me.
Switched to NixOS and definitely still not an expert, but it’s simple enough that 4 machines are running it. I really enjoy it. Already migrated a critical machine, where I basically used a second machine for A/B testing, to ensure minimal downtime and rollback possibility.
My deploy story is still kinda jank. I just looked at what worked and didn’t read too much about the internals. Using deploy-rs and falling back to nixos-anywhere when necessary.
Some new services were really basically as easy as adding
services.example.enabled = true;and deploying.Hope it helps an good luck!
Do you think the lack of apparmor or selinux is a problem for nixOS?
Personally didn’t worry about it. Some issues in CoreOS with SELinux left a sour taste; tried to get my reverse proxy running, but a policy was missing and I either had to compile custom policies or turn off enforcement.
In NixOS, I was careful about checking file permission setup, service users and systemd service hardening options for the services I’m running. Defaults on what I installed seemed pretty good hardening, better than what I’d do myself.
I think it’s easy to overlook as a first time user that everything in the nix-store is readable to all, so no secrets in there, anywhere. I ended up using sops-nix.