Retire the standing flakes? / nixos-hardware TODOs in the README.
Motivation. szaffarano/nix-dotfiles (see README → Related configs) shows the mature end-state for a repo with our exact "keep Ansible and Nix" philosophy: a flake pinning nixos-hardware, so the Framework laptop quirks for artus/margo come from nixos-hardware.nixosModules.framework-* upstream instead of being hand-maintained here.
Scope.
- Add
flake.nix / flake.lock; expose nixosConfigurations.{artus,margo,jolly,...}.
- Pull hardware modules from
nixos-hardware for the Framework hosts.
- Keep the channels-based path working during transition;
configuration.nix stays a reference entrypoint.
- Follow-on (separate, once on flakes): add
renovate.json for automated flake.lock bumps.
Constraint — jolly. Do NOT live-switch the graphical stack on jolly; prepare upgrades for the next boot (see docs/jolly.md). The migration must respect this — no nixos-rebuild switch on jolly as part of cutover.
Open decision. Whether to adopt home-manager at the same time is deliberately out of scope here — tracked separately.
Retire the standing
flakes?/nixos-hardwareTODOs in the README.Motivation.
szaffarano/nix-dotfiles(see README → Related configs) shows the mature end-state for a repo with our exact "keep Ansible and Nix" philosophy: a flake pinningnixos-hardware, so the Framework laptop quirks forartus/margocome fromnixos-hardware.nixosModules.framework-*upstream instead of being hand-maintained here.Scope.
flake.nix/flake.lock; exposenixosConfigurations.{artus,margo,jolly,...}.nixos-hardwarefor the Framework hosts.configuration.nixstays a reference entrypoint.renovate.jsonfor automatedflake.lockbumps.Constraint —
jolly. Do NOT live-switch the graphical stack onjolly; prepare upgrades for the next boot (seedocs/jolly.md). The migration must respect this — nonixos-rebuild switchon jolly as part of cutover.Open decision. Whether to adopt
home-managerat the same time is deliberately out of scope here — tracked separately.