Gabriel Arazas
3324c12d4c
Now, there could be multiple wrappers within the configuration but it should still result with one derivation unlike the original version. This could be handy for making package overrides with multiple binaries (for example, 7Z) while making the interface consistent. This turns out to be way nicer than I thought which is a good thing. |
||
---|---|---|
.. | ||
disko | ||
flake-parts | ||
home-manager | ||
nixos | ||
nixvim | ||
README.adoc |
This is the folder containing various configurations for various environments, typically the ones configured using the Nix module system such as NixOS, home-manager, and nixvim. Each of these configurations are assumed to use custom modules defined at ../modules/ (where it has similar folder structure).
Furthermore, these configurations do have a certain "codename" in the commits for easier inspection of the history. Here is the following list of them used in the repo history:
-
diskoConfigs
for Disko configurations. -
hosts
for NixOS systems (e.g.,hosts/ni
). -
users
for home-manager configurations (e.g.,users/foo-dogsquared
). -
nixvimConfigs
for NixVim configurations (e.g.,nixvimConfigs/fiesta
). -
flake
for flake-parts (seeing it only has one of them, it is constantly referred to asflake
).
These "codenames" are also used for their environment-specific module structuring (e.g., hosts.ni.services.backup.enable
for NixOS, nixvimConfigs.fiesta.setups.tree-sitter
for NixVim, users.foo-dogsquared.setups.desktop.enable
for home-manager) with the exception of flake-parts where it is basically a free-for-all.
Lastly, these modules are referred collectively in the commits as modules
.