8000 GitHub - Bad3r/nixos: NixOS Infrastructure as Code using the Dendritic Pattern & flake parts · GitHub
[go: up one dir, main page]

Skip to content
Bad3rPublic

About

NixOS Infrastructure as Code using the Dendritic Pattern & flake parts

Topics

Resources

Stars

9 stars

Watchers

1 watching

Forks

Repository files navigation

NixOS logo

NixOS Configuration

NixOS Infrastructure as Code using the Dendritic Pattern, an organic configuration growth pattern with automatic module discovery. Powered by flake-parts.

The system76 host (System76 Oryx Pro laptop) and the tpnix host (ThinkPad P15s Gen 2i laptop) are deprecated: their configurations were removed from this repository in #489 and #597 and survive only in git history.

Automatic Import

All Nix files are flake-parts modules and are automatically imported via import-tree. Files prefixed with _ are omitted. No literal path imports are used, so files can be moved and nested freely.

Shared device policy that serves multiple optional applications belongs in modules/hosts/common/, so its permissions do not disappear when one app module is disabled. Optional app modules own their package and capability-wrapper behavior, including compiled argv filters with audited, grammar-aware allowlists that fail closed on unsupported and non-device forms, validate parser-dependent argument boundaries, and bound the resulting no-sudo operation boundary.

Build and Deployment

This project uses a custom build script, build.sh, for validation and deployment:

./build.sh              # validate and deploy
./build.sh --boot       # install for next boot only
./build.sh --update     # refresh metadata + update flake inputs
./build.sh --offline    # Offline build

The script runs a validation pipeline (format, pre-commit hooks, flake check) before deployment. It refuses to run on a dirty worktree by default; use --allow-dirty to override. --update intentionally allows dirty worktrees and does not auto-commit flake.lock.

Development commands:

Command Description
nix develop path:. Enter dev shell
nix run path:.#treefmt -- . Format files
nix develop path:. -c pre-commit run --all-files --hook-stage manual Run all hooks

These carry the explicit path:. installable because the branch workflow in AGENTS.md puts the work in a linked worktree, where Lix cannot fetch a clean checkout as a git+file flake: .git is a file there, not a directory. Dropping path:. gives the primary-checkout form, where nix fmt also works. Two cases path:. cannot fix: nix fmt, because Lix hardcodes the . installable in lix/nix/fmt.cc; and any command that writes flake.lock back, such as nix flake metadata --refresh and nix flake update, which need an absolute ref like "path:$PWD".

Home Manager Package Pattern

NixOS app modules own each app's row and package. Home Manager modules configure the app, gate on its row, and set package = null where Home Manager supports it or take the package from the row otherwise.

See Home Manager app modules for details.

App Wiring

Nested host app overrides register full option paths and route them through programs first, then services for services-only paths. A path absent from both baseline namespaces fails the host evaluation, so it cannot be dropped by a switch that never runs the FR-5 check.

See App registry for the routing and validation contract.

Storage Boundaries

Storage-dependent services must be enabled only on hosts that provide their required mount. songbird owns the dedicated /data volume that backs the common local mirror writers and the R2 runtime.

See the local mirror reference and R2 runtime policy for the operational contracts.

Cache Boundaries

Cache-root membership is derived from evaluated host configuration. Every NVIDIA-enabled host explicitly sets cacheRoots.nvidiaKernelModules; missing, malformed, or unknown policy values fail evaluation. songbird sets it to false to keep its source-built CachyOS module out while retaining nvidia-x11 and nvidia-settings coverage.

See binary cache coverage for the inventory and operator policy.

Secrets

Secrets are managed with sops-nix. Encrypted payloads live in secrets/, a private git submodule, and are declared via sops.secrets.

See the sops documentation for usage instructions.

Flake Input Deduplication

These root inputs pin shared dependencies used through .follows declarations. systems keeps the canonical nix-systems input name even though dependency inputs also follow it. The table lists dedicated dedupe roots and canonical non-nixpkgs roots; ordinary root followers such as nixpkgs are declared beside each dependent input. Remove any dedupe_* input once no .follows declaration references it.

Input Followed By
dedupe_flake-compat make-shell.inputs.flake-compat, nix-cachyos-kernel.inputs.flake-compat
dedupe_nur stylix.inputs.nur
systems stylix.inputs.systems

About

NixOS Infrastructure as Code using the Dendritic Pattern & flake parts

Topics

Resources

Stars

9 stars

Watchers

1 watching

Forks

Releases

< 335C div class="sidebarSection__oqw6Y8">

Packages

Used by

Contributors

Languages

0