sops-nix VS flake-utils-plus

For applications, I think environment variables are great. Especially if you adopt nomad because you could also use vault to populate secrets in. For machines that won't work so you'll need something else like https://github.com/Mic92/sops-nix

I've heard good things about and seen sops-nix used on a few really solid configs. Others tend to use Age or Homeage.

You can use something like sops-nix if you're on NixOS https://github.com/Mic92/sops-nix.

Yeah, I don't know how to manage secrets yet. I've read about sops-nix, but I don't have the slightest clue how to integrate it into my own nix-config.

I use sops-nix for that. Secrets are stored encrypted in the store, and decrypted at runtime.

One think I saw that I don't recommend is to change your password after installing; that's not very reporoducible, use users.users..hashedPassword or users.users..passwordFile with agenix or sops-nix.

So, I did some digging. According to the first Dicourse chat that popped up, it's "not possible". That's not an acceptable answer for me ;). I read through HM's appendix to see if there's a mention of private keys there (there weren't). I also know of SOPS (and sops-nix), but that seems to require an SSH/GPG key to decrypt :D.

If you only need secrets management, there are quite a lot of bolt-on solutions with little overhead which are also agnostic to the form of deployment, like https://github.com/Mic92/sops-nix or https://github.com/ryantm/agenix. Personally for my machines I want unattended reboots, so I just copy all keys to the hard disk and manage secrets solely with file permissions.

You don't need channels to use nix-shell or nix-env. You can generate the Nix path and registry from your flake inputs. flake-utils-plus makes this easy with nix.generateRegistryFromInputs and nix.generateNixPathFromInputs.

Use flake-utils-plus to easily define multiple systems in flake.nix.and then use the --target-host flag of nixos-rebuild to deploy it remotely.

If you're trying to handle multiple systems with one config a flake is a significantly better option. I would personally recommend looking at flake-utils-plus and specifically this example config.

I looked at some past threads / examples and saw people recommend flake-utils-plus, but after reading the examples I don't understand how I would get home-manager on Darwin or Ubuntu.

Depending on your specific needs, the channelsConfig (modify arguments passed to Nixpkgs) and overlay tooling in flake-utils-plus may be adequate: https://github.com/gytis-ivaskevicius/flake-utils-plus/tree/...

For flakes you don't have to set up everything manually there are helper libraries, I use flake-utils-plus.

Converting to flakes is not that hard if you use a good library. The documentation is other people's configs, really.

Neat! I've been using flake-utils-plus's implementation until now. https://github.com/gytis-ivaskevicius/flake-utils-plus/blob/master/lib/repl.nix

I use flake-utils-plus based configuration to apply patches on top of nixpkgs where overlays don't suffice.