nixos-config VS digga

---

With NixOS you declare your entire OS in a script, something along the lines of Ansible or Terraform. This can even go as far as configuring your user settings, with dotfiles, gsettings, or various other things (often the modules will expose settings in the native nix language and write out the yaml/toml/json/whatever else that is required). The idiomatic way to do this is to use the built-in NixOS configuration (under /etc/nixos) to set up system-level things: mounts, drivers, users, system-level packages (e.g. greetd+sway), and things that change rarely. You then use a project called home-manager to manage everything inside your user configuration (including applications you use), which itself uses nix. By separating it like this, I can sync my entire experience between my laptop and desktop with Git.

I am currently flighting using a separate "nix flake" for both, which allows you to pin versions of packages (with a lockfile). It also allows you to easily pull in other repositories. It hasn't really taken off yet, and the NUR (Nix User Repository, analogous to the amazing Arch User Repository) is still in infancy. I'd offer up my nix configs as an example, but I am currently in the "make it work" example. I have been yoinking several great ideas from this fantastic nix repo: https://github.com/ymatsiuk/nixos-config

The main challenge with Nix is that it doesn't have an FHS: there is no `/usr`, `/bin`, and what you would typically expect. The advantage here is that conflicting dependency versions are not a problem. The problem is that you need to either build any binaries yourself, or wrap them in an FHS helper.

Nix has a virtualenv system `nix develop` and it's very powerful, especially for teams.

Silverblue

This one issue may clear things up, seems like my config is a little outdated: https://github.com/divnix/digga/pull/385

I'm new to the Nix world, but so far I've come across Divnix's Digga, Numtide's DevShell, and Misterio77's nix-starter-configs.

There are config templates / configuration helper libraries that try to make this easier, for example digga/devos.

https://nixos.wiki/wiki/Flakes, especially the “see also” section. If you’re looking to use for NixOS config across multiple hosts, digga (see the repo for example template) is pretty nice for encapsulating a lot of boilerplate.

The digga library, while being more complex to use than other solutions here, got a pretty elegant solution for it merged a few weeks ago. Still some cracks that are getting smoothed over, but it seems to work.

I like the concept digga/devos uses (unfortunately their stuff kind of is an overengineered incomprehensible mess): They use: - modules: for modules like in nixpkgs (i.e. stuff that defines options and generates configuration based on that options; are included into every host) - profiles: concrete configuration, can be included to host definitions - suites: sets of profiles (so you can for example have a desktop suite with all your profiles with "desktop" configuration options and apply that to all your desktop computers)

For the system, I like the devos template:

https://github.com/divnix/devos

The idea of flakes is how you define inputs, and you define the system (and packages, and shell etc.) in the outputs using the inputs. The inputs are git repos which point to other flakes. You can mix and match these as much as you want (see the devos repo for examples) and when you build the derivation, it generates a lockfile for exact commits in that point in time what were used in the given inputs.

You commit the lockfile and in the other systems where you pull your config from the repo, it uses exactly those commits and installs the same versions as you did in your other systems.

This was quite annoying and hard to do before flakes. Now it's easy.

The problem what people face with building their system as a flake is combining the packages so you can point to `jq` from the unstable nixos and firefox from the stable train. I think this aspect needs better documentation so it wouldn't be so damn hard to learn (believe me, I know). Luckily there are projects like devos that give a nice template for people to play with (with documentation!)

Another use for flakes is to create a development shell for your repo, an example what I did a while ago:

https://github.com/pimeys/nix-prisma-example

Either have `nix-direnv` installed, enter the directory and say `direnv allow`, or just `nix develop` and it will gather, compile and install the correct versions of packages to your shell. Updating the packages? Call `nix flake update` in the directory, commit the lockfile and everybody else gets the new versions to their shell.

Yes, I put the repository in ~/nix. My repository is based on devos, but I am thinking of switching to a different setup, because I don't want to depend on a framework which can be an issue in updating.

I no longer use the official way since I have switched to flakes. I am currently using a devos-based config, which is a boilerplate that depends on a Nix toolchain, but I plan on rewriting the config with flake-utils-plus. You probably can install home-manager using deploy-rs. See the following comment: