Files

Check / eval (push) Successful in 4m16s

Details

feat(flake): #134 — unstable.<pkg> in the downstream, one input, no hand pins

Nomarchy now carries a nixpkgs-unstable input and exposes it through
overlays.default as an `unstable` attrset: in the template's
`home.packages = with pkgs; [ … ]` a user writes `unstable.lmstudio`
and is done. Downstream stays one locked input; nomarchy-pull moves it.
lib.nix needed zero changes — mkFlake's pkgs already applies the
overlay. The import is plain and non-recursive, so configs that never
reference unstable. pay nothing beyond the input fetch; allowUnfree
mirrors the base set so the motivating lmstudio resolves.

Home packages are the supported surface (documented convention). Costs
stated in the README, not hidden: you own the pinned+unstable
combination; a second toolchain lands in your closure (~690 of ~4k
paths shared, measured on lmstudio); it moves when the lock moves.
Lock bumps now move two channels — VERIFICATION §5 and CONVENTIONS
updated accordingly. flake.lock gained exactly one node
(nixos-unstable @ 753cc8a); nothing else moved.

Verification: V1 — nix flake check --no-build green; new eval-only
checks.unstable-seam green (26.05pre vs 26.11pre lib.version, no
builds); template HM activation built via mkFlake with unstable.hello
enabled and its closure carries the unstable store path (pg2zfr… vs
pinned nm7p8w…). Implementation by a Sonnet subagent; design and
review on Fable.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

2026-07-17 15:16:29 +01:00

flake.nix

fix(install): bake dconf, seed main, name ISO, display modes (#123–#126)

2026-07-15 09:58:53 +01:00

hardware-configuration.nix

feat: nomarchy.lib.mkFlake — one-call downstream wrapper + hardware profiles

2026-06-10 15:39:21 +01:00

home.nix

feat(flake): #134 — unstable.<pkg> in the downstream, one input, no hand pins

2026-07-17 15:16:29 +01:00

README.md

refactor(#107 ): theme-state.json → state.json, theme-sync → state-sync

2026-07-15 11:26:59 +01:00

state.json

refactor(#107 ): theme-state.json → state.json, theme-sync → state-sync

2026-07-15 11:26:59 +01:00

system.nix

feat(power): suspend-then-hibernate 1h on battery (#115 )

2026-07-15 12:13:23 +01:00

README.md

My Nomarchy machine

This directory is the single source of truth for a Nomarchy machine flake. nix flake init -t … copies it as-is; nomarchy-install copies the same files and only patches install-time values (username, hostname, keyboard, detected hardware, password hash, …). Keep commented opt-ins and home.packages here — do not invent a second catalog in the installer.

Overwrite the placeholder hardware config with the real one: nixos-generate-config --show-hardware-config > hardware-configuration.nix
Set flake.nix up once (Nomarchy repo URL, your username, optionally a hardwareProfile from https://github.com/NixOS/nixos-hardware — an unknown name fails the rebuild with suggestions). After that the flake is never touched again: your machine lives in system.nix (hostname, services — the login user is created from username automatically) and home.nix (your packages).
git init && git add -A — flakes only see tracked files, including state.json.
System: sudo nixos-rebuild switch --flake .#default
Desktop: nix run home-manager -- switch --flake .#me (afterwards just home-manager switch --flake .#me — it's installed)
Clone/symlink this directory to ~/.nomarchy (or export NOMARCHY_PATH) so nomarchy-state-sync knows where the state lives.

Day-to-day:

nomarchy-state-sync list             # 24 shipped presets
nomarchy-state-sync apply gruvbox    # writes state + home-manager switch
nomarchy-state-sync bg next          # cycle wallpapers (instant, no rebuild)

The system layer only needs nixos-rebuild when you change system.nix.