Skip to content
Oeiuwq Faith Blog OpenSource Porfolio

Lord-Valen/configuration.nix

Lordly NixOS Configurations

Lord-Valen/configuration.nix.json
{
"createdAt": "2022-03-14T20:29:56Z",
"defaultBranch": "main",
"description": "Lordly NixOS Configurations",
"fullName": "Lord-Valen/configuration.nix",
"homepage": "",
"language": "Nix",
"name": "configuration.nix",
"pushedAt": "2026-07-10T23:25:19Z",
"stargazersCount": 29,
"topics": [
"dendritic",
"dendritic-nix",
"dotfiles",
"emacs",
"home-manager",
"nix-flake",
"nixos",
"nixos-config",
"nixos-configuration",
"nixos-dotfiles",
"stylix"
],
"updatedAt": "2026-07-10T23:25:23Z",
"url": "https://github.com/Lord-Valen/configuration.nix"
}

Inputs are pinned with nixtamal and resolved with with-inputs. There is no flake.lock; pins live in [nix/tamal/lock.json]!(nix/tamal/lock.json).

FilePurpose
default.nixPrimary entry point; returns full flake outputs
configuration.nixConvenience entry point; selects the NixOS config for the current hostname (impure — reads /etc/hostname)
flake.nixThin shim so flake-aware tools still work
Terminal window
nh os switch -f ./configuration.nix
Terminal window
nixtamal refresh # refresh all non-frozen inputs
nixtamal refresh <name> # refresh one input
nixtamal check-soundness # verify all fetches resolve

See definition at [readme.nix]!(modules/meta/files/readme.nix).

The set of NixOS hosts is defined via an option which accepts deferred modules. Differentiating the hosts as a subset of the NixOS modules allows us to map over the hosts without string matching.

See usage at [autolycus]!(modules/hosts/autolycus/default.nix).

Closure size checks are defined via the closureChecks option. Each entry logs the human-readable closure size; an optional budget field causes the check to fail if the size exceeds it.

See checks at [closureChecks/]!(modules/closureChecks/).