kevinveenbirkenbachandClaude Opus 5
5137465c6f
3529 invalid comments in 528 files, grandfathered in while the linter only saw the working-tree diff. Removal ran through the linter's own collectors, so detection and deletion cannot drift: a comment whose opener line is blank before it and whose closer line is blank after it loses all its lines, anything else loses only the comment region, and a line left holding a bare delimiter goes with it. Five files keep their comments behind a nocheck marker instead. Four are upstream configs whose inline docs are upstream's own (mautrix, systemd journald, nextcloud-oidc-login, MediaWiki). In littlejs the commented-out entries ARE the deactivation mechanism for an example tile, so deleting them would delete configuration. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
User
Description
This role configures a basic user environment (shell dotfiles and SSH authorized_keys)
for a user selected via user_key.
Overview
This role executes common tasks for user environment configuration.
Cosmos
The diagram places User in the Infinito.Nexus cosmos: the components it deploys (capabilities), the central services it consumes (dependencies), and its outward reach (federation and bridged external networks).
flowchart LR
subgraph role [user 💻]
svc_user["user"]
end
Solid 1:1 edges are fixed relationships; dashed 0..1 edges are conditional (enabled only in matching deployments); red 0..0 edges are turned off in this role. Node markers show the role's deploy modes (💻 host, 🐳 compose, 🐝 swarm); ❌ marks a service that is explicitly turned off, and ⚙️ an Ansible role dependency declared in meta/main.yml.
Features
- Automated provisioning: Configured by Ansible without manual steps.
User data resolution
User data is resolved via lookup('users', user_key) and referenced via user_key.
Callers may pass user_config to override the resolved lookup result for one invocation.
Resolution rules:
user_usernameis resolved fromlookup('users', user_key).username(fallback:user_key)- Home path and ownership are based on
user_username - SSH keys are read from
lookup('users', user_key).authorized_keys
Required input
user_key
Optional user fields
lookup('users', user_key).username(defaults touser_key)lookup('users', user_key).authorized_keys(list; may be empty)- optional include-role var
user_configto override the lookup result for the current call
Credits
Implemented by Kevin Veen-Birkenbach. Part of the Infinito.Nexus Project and maintained by Kevin Veen-Birkenbach. Licensed under the Infinito.Nexus Community License (Non-Commercial).