nixos-config/configs
Gabriel Arazas 3324c12d4c
wrapper-manager-fds/modules: overhaul wrapper config
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.
2024-07-08 21:12:31 +08:00
..
disko diskoConfigs/archive: init 2024-02-27 21:05:49 +08:00
flake-parts users/foo-dogsquared: integrate wrapper-manager-fds 2024-07-05 17:56:38 +08:00
home-manager wrapper-manager-fds/modules: overhaul wrapper config 2024-07-08 21:12:31 +08:00
nixos hosts/{bootstrap,graphical-installer}: fix config 2024-06-21 16:10:50 +08:00
nixvim nixvimConfigs/fiesta: update deprecated lua attribute for keymaps 2024-06-27 18:30:37 +08:00
README.adoc docs: update READMEs 2024-03-01 18:12:55 +08:00

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 as flake).

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.