chore: EDaaS systemd linger hardcoded to a literal username #48

New Issue

2026-06-29T12:29:55+01:00

lyrathorpe commented

2026-06-29 12:29:55 +01:00

Problem

hosts/EDaaS/configuration.nix set users.users.emmathorpe.linger = true with the username hardcoded in the host config, separate from where the account itself is defined.

Impact

Per-user system state scattered across host files; brittle if the host's user changes.

Resolution

Linger is now an opt-in flag in the host table's users set, applied by modules/users.nix only when set. Fixed by the user-registry refactor.

## Problem `hosts/EDaaS/configuration.nix` set `users.users.emmathorpe.linger = true` with the username hardcoded in the host config, separate from where the account itself is defined. ## Impact Per-user system state scattered across host files; brittle if the host's user changes. ## Resolution Linger is now an opt-in flag in the host table's `users` set, applied by `modules/users.nix` only when set. Fixed by the user-registry refactor.

lyrathorpe referenced a pull request that will close this issue

2026-06-29 12:30:53 +01:00

refactor(flake): user registry, multi-user hosts, and portable home outputs #49

lyrathorpe closed this issue

2026-06-29 13:06:25 +01:00

lyrathorpe referenced this issue from a commit

2026-06-29 13:06:26 +01:00

refactor(flake): user registry, multi-user hosts, and portable home outputs (#49)

Sign in to join this conversation.