docs: simplify code comments, keep the detail in the README
CI / flake (pull_request) Successful in 3m27s
CI / flake (pull_request) Successful in 3m27s
The registry / multi-user / portable-home rationale lives in the README (Users, Hosts, Portable home); the corresponding code comments are reduced to one-liners that point there. No functional change (host derivations are unchanged).
This commit is contained in:
+3
-9
@@ -1,9 +1,5 @@
|
||||
# System-level user accounts, built from the identity registry
|
||||
# (users/registry.nix). `hostUsers` is the host's user set, threaded by mkHost
|
||||
# from the flake host table; `userRegistry` is the global identity table passed
|
||||
# as a specialArg. Every account's identity -- description, groups, authorized
|
||||
# keys -- comes from its registry entry, so no user data is hardcoded here and a
|
||||
# host may declare any number of users.
|
||||
# System user accounts, built from the registry (users/registry.nix) for the
|
||||
# host's `hostUsers` set. See README "Users".
|
||||
{
|
||||
config,
|
||||
pkgs,
|
||||
@@ -29,9 +25,7 @@
|
||||
openssh.authorizedKeys.keys = id.sshAuthorizedKeys;
|
||||
shell = pkgs.zsh;
|
||||
}
|
||||
# Keep this user's systemd --user instance running without an open login
|
||||
# session (e.g. for home-manager user timers). Only emitted when the host
|
||||
# table opts in, so hosts that don't set it leave linger entirely unmanaged.
|
||||
# linger opt-in (host table); left unmanaged when unset.
|
||||
// lib.optionalAttrs (spec ? linger) { inherit (spec) linger; }
|
||||
) hostUsers;
|
||||
|
||||
|
||||
Reference in New Issue
Block a user