home-rpickler

rpickler's personal home configuration as a standalone flake — extracted from richardpickler.com/nixos/users (the users/ layout is kept: users/users/rpickler.nix persona, users/modules/ modules, users/hosts/ per-machine overlays).

This flake exports module sets and owns no system: whoever builds a machine composes it. That is the seam both consumers use:

richardpickler.com/nixos (household)      SeesDeployment workstation-flake
        │  nixosConfigurations                │  users/rpickler.nix adapter
        └──────────────┬──────────────────────┘
                       ▼          home-rpickler (this repo)
              hmModules.rpickler  +  byHost."<hostname>"

Use it

As an input (both consumers):

inputs.home-rpickler = {
  url = "git+https://git.richardpickler.com/richardpickler.com/home-rpickler.git";
  inputs.nixpkgs.follows = "<your nixpkgs>";  # keeps useGlobalPkgs coherent
};

nixpkgs-unstable, nixvim, home-manager, elephant are also exposed as follow-points so a consumer can guarantee there is exactly one copy of each on a system (the SeesDeployment aggregator follows all of them).

Household NixOS system (home-manager.nixosModules.home-manager):

home-manager = {
  useGlobalPkgs = true;
  useUserPackages = true;
  extraSpecialArgs = { seesHome = { inherit inputs self; hostname = <hostname>; }; };
  users.rpickler = import ./compose-rpickler.nix;  # hmModules.rpickler
                                                     # ++ byHost.<hostname>
};

If you pass this flake's own inputs as seesHome.inputs, set seesHome.hostname = config.networking.hostName so host-overlays.nix picks the per-machine file; the flake's byHost.<hostname> does exactly that with the flake's own inputs.

Standalone per-user (home-manager.flakeModules.home-manager) — the nixd-style user-level daemon story from SeesDeployment issue #16: same module list, home-manager invoked directly, seesHome.hostname from builtins.currentSystem-adjacent config or left unset.

SeesDeployment aggregator — workstation-flake/users/rpickler.nix is the adapter; nothing here knows about machines, machines.nix owns that.

Update flow

nix flake update home-rpickler on each consumer, then a normal rebuild — nixos-rebuild switch --flake on household machines, and the aggregator's single command (or its auto-upgrade daemon) on Sees.AI workstations.

Extraction notes (deliberate deltas from the household copy)

• Modules are verbatim except two seam edits, each commented in place: users/modules/default.nix is now the shim that injects pkgs/inputs/ specialArgs (the household system layer used to pass them via extraSpecialArgs), and backup.nix gets sops-nix via seesHome.inputs.
• Secrets did not move. sops.nix still points at the household repo's modules/secrets.yaml path (per-machine); backup.nix (restic) is dormant behind backup-seam.nix. Re-enable is one imports line.
• gnome.nix was not extracted — dead import for the hyprland persona.
• Per-host layouts became users/hosts/<host>.nix + host-overlays.nix (the old "@${hostname}" key mechanism); kansas.nix's monitor list lost its mkForce (flagged TODO(extraction) in the file).
• This repo is public; the household repo is private. Nothing secret is in here by construction, but note backup.nix carries the household restic server URL (the passphrase never was in the clear) — rotate if it matters.