.dots VS nixos-config

I have a wrapper function that just maps to dev to make life easier: https://github.com/dmadisetti/.dots/blob/template/dot/config/fish/functions/develop.fish

Never fully got it to work, so I just encrypt my secrets when I build my isos: https://github.com/dmadisetti/.dots/actions/runs/5055636638/jobs/9072093945

I have multiple files for each machine based on hostname. I have CI strip my config of all system specific information for general distribution. For reference: https://github.com/dmadisetti/.dots

I build a wsl image: https://github.com/dmadisetti/.dots/blob/template/nix/machines/wsl.nix

What I do: Keep secrets in a separate git repo as a flake, and have a stub flake, that can be overridden: https://github.com/dmadisetti/.dots/tree/template/nix/spoof

My dots

I have a script that will symlink my dotfiles in (github:dmadisetti/.dots/setup.sh), because you also end up with weird RO permissions if you do it through Nix. I think this is fine. It also means that you aren't stuck with Nix

The way I manage multiple systems is with a wrapper: https://github.com/dmadisetti/.dots/blob/template/dot/config/fish/functions/snix.fish

The only thing that is semi manual is setting up disks on first install (something you'd still have to do with arch). You can still script that: https://github.com/dmadisetti/.dots/blob/template/scripts/run-install.nix.sh

balsoft: https://github.com/balsoft/nixos-config

Examples: - https://github.com/gmarmstrong/dotfiles/blob/master/nixpkgs/home.nix - https://github.com/balsoft/nixos-config/blob/master/profiles/applications-setup.nix - https://github.com/gytis-ivaskevicius/nixfiles/blob/master/home-manager/common.nix - https://github.com/xtruder/nix-profiles/blob/master/home-manager/roles/desktop/work.nix

I am not in a state to write a detailed recommendation list for all the things you've mentioned, but: - There is indeed an official Matrix room: #nix:nixos.org . I believe this is the most popular Nix community out there. - As for multiple hosts, there are different approaches out there. Typically you will write NixOS "modules" (which are like pieces of configuration) and then merge (combine) them together, along with some machine-specific overrides, to get configurations for all your machines. I do something similar for my config. Here are the modules: https://github.com/balsoft/nixos-config/tree/master/profiles which configure different pieces of my system, then those modules are combined into "roles" (e.g. here's a desktop role: https://github.com/balsoft/nixos-config/blob/master/roles/desktop.nix) and then those roles are imported from actual machine configs with some overrides (e.g. here's the config for the box I'm writing this from: https://github.com/balsoft/nixos-config/blob/master/machines/AMD-Workstation/default.nix)

Hey, inkscape build seems to be broken, but I have made a new working derivation that uses resvg instead: https://github.com/balsoft/nixos-config/blob/master/modules/workspace/gtk.nix#L32

I use a custom pass-based hack: https://github.com/balsoft/nixos-config/blob/master/modules/secrets.nix and https://github.com/balsoft/nixos-config/blob/master/modules/secrets-envsubst.nix. My actual GPG key is on my yubi.

Adding self to local registry is done here: https://github.com/balsoft/nixos-config/blob/master/modules/nix.nix#L6

Ok, just checked with that nix version and my nixos-config, and I can build my configuration without .git in it.