nixos-config/configs
Gabriel Arazas e4e133dc9f
Some checks failed
Build devcontainers / build-devcontainers (push) Has been cancelled
Cache outputs / build-custom-packages (push) Has been cancelled
Check flake outputs / check-outputs (push) Has been cancelled
Publish every Git push to master to FlakeHub / flakehub-publish (push) Has been cancelled
Build personalized bootstrap ISO / build-iso (x86_64-linux) (push) Has been cancelled
Build project site / build (push) Has been cancelled
Build project site / deploy (push) Has been cancelled
Update Firefox addons / update-firefox-addons (push) Has been cancelled
users/foo-dogsquared/dotfiles: update packages for Neovim "distribution"
2025-01-24 18:44:14 +08:00
..
disko diskoConfigs/laptop-ssd: update mount options 2025-01-01 16:26:58 +08:00
flake-parts hosts/ni: set Nushell as default user shell for foo-dogsquared user 2025-01-22 13:36:31 +08:00
home-manager users/foo-dogsquared/dotfiles: update packages for Neovim "distribution" 2025-01-24 18:44:14 +08:00
nixos hosts/ni/services/rss-reader: add helper script 2025-01-15 14:00:26 +08:00
nixvim nixvimConfigs/fiesta: update LSP and Treesitter setup 2025-01-21 13:37:11 +08:00
wrapper-manager wrapperPackages/dotfiles-wrapped: add Zellij wrapper 2024-10-04 17:09:08 +08:00
README.adoc docs: document conventions for setting module arguments 2025-01-24 18:42:23 +08:00

Table of Contents

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

  • wrapperPackages for wrapper-manager packages (e.g., wrappers/archive-setup).

  • 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.

Conventions

Theres a few things you need to remember for these configurations.

  • Module arguments that are only suitable to be included in the first build step of the configuration are all under the firstSetupArgs namespace.

  • Module arguments that are only found inside of the configuration itself should be under the configurationArgs namespace.