rushabhp-droid/nixos-conf

1. Overall shape

This is a single-host Nix flake that produces a reproducible NixOS system plus a Home Manager user environment. The repository is organized around a clear split between machine-wide configuration and user-session/dotfiles configuration.

2. Entry points

flake.nix is the top-level composition layer. It pulls in inputs, exposes outputs, and wires together the host definition under hosts/laptop/ with shared modules under modules/. treefmt.nix and .pre-commit-config.yaml define the repository’s code-quality boundary.

3. Host layer

hosts/laptop/configuration.nix is the NixOS entry point for the laptop. It combines the hardware declaration (hardware-configuration.nix, disk-config.nix) with the reusable NixOS modules. This is where the system becomes a specific machine profile rather than a generic module set.

4. System-wide subsystems

modules/nixos/ contains the OS-level responsibilities: core system setup, users, security, hardware tweaks, NVIDIA-specific support, fonts, gaming/Steam, auto-refresh, and secret integration. These modules shape boot-time behavior, drivers, services, and privileged configuration.

5. User-session subsystem

hosts/laptop/home/home.nix hands off to modules/home-manager/, which defines the user environment. This layer owns shell, terminal, editor, compositor session config, notification tools, and desktop utilities. It is separate from the OS layer so user preferences can evolve independently of the machine config.

6. Desktop environment stack

The session is Wayland-centric and centered on Hyprland. Supporting pieces include waybar for the panel, rofi for launching, hypridle and hyprlock for session locking/power behavior, plus swaync, swayosd, and wleave for notifications, on-screen display, and logout flow. The raw/ directories hold the actual config assets consumed by those modules.

7. Configuration flow for the desktop

The Hyprland setup is split into Lua fragments under modules/home-manager/desktop/raw/hyprland/ for animation, autostart, colors, general settings, keybinds, and rules. Waybar has separate JSON/CSS assets under raw/waybar/. This indicates a pattern where Nix modules install and parameterize the apps, while raw files define the exact runtime configuration.

8. Theming and visual coherence

modules/home-manager/system/stylix.nix and the README point to Stylix as the global theme engine. Styling is propagated across the OS and desktop apps, with shared colors/fonts feeding Waybar, Rofi, terminal appearance, and other UI elements. This is a cross-cutting concern rather than a single app feature.

9. Shell, terminal, and CLI tools

The CLI side is grouped under modules/home-manager/cli/ and includes alacritty.nix, helix.nix, and zsh.nix. These define the interactive developer environment at the user level, sitting alongside the graphical desktop stack.

10. Secrets boundary

modules/nixos/system/sops.nix and modules/nixos/system/secrets/ handle sensitive data via sops-nix with age-encrypted secrets. The encrypted secrets.yaml is the source of truth; at evaluation/runtime it becomes injected into system services or users without exposing plaintext in the repo.

11. Hardware and platform-specific behavior

The repository includes dedicated hardware tuning modules, especially for NVIDIA/hybrid graphics and power management. That suggests the architecture is intentionally tuned for this laptop’s runtime constraints rather than being a generic desktop template.

12. Operations and maintenance

The repo is designed to be managed through Nix workflows: rebuilds via nh, updates via nix flake update, and formatting/linting via nix fmt plus pre-commit hooks. In diagram terms, the “control plane” is the flake/dev-shell tooling, while the “data plane” is the generated OS and user configuration applied on the machine.

13. What to draw

A useful diagram would show: flake inputs → host config → NixOS modules + Home Manager modules → runtime system services and user apps, with side branches for hardware-specific tuning, secrets injection, and theme propagation through Stylix into the desktop stack.