feat(titan): Zenbook laptop on a shared workstation profile

terra's desktop is split into profiles/workstation.nix (NixOS side) and
home/desktop/ (home-manager side, moved from hosts/terra/home*), so titan,
an ASUS Zenbook Pro Duo UX581 (Intel iGPU + RTX 2060 PRIME offload),
gets the same Hyprland workstation. Per-host monitors, primary/secondary
output and wallpaper are homelab.desktop.* options; the quickshell widgets
read the outputs from QS_PRIMARY_OUTPUT/QS_SECONDARY_OUTPUT instead of
hardcoding DP-2/HDMI-A-1. Folder icons come from a new HyprChrome-Folders
icon theme.

titan gets its own sops file and recipient. LibreChat is removed from
terra along with its secrets declarations.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-10-21 11:33:03 +02:00
co-authored by Claude Opus 5.5
parent e191ea3c8a
commit 760e353335
25 changed files with 652 additions and 279 deletions
+1 -26
View File
@@ -4,6 +4,7 @@
# decrypted with terra's own SSH host key (recipient in ../../.sops.yaml).
# The host key is pre-generated on the laptop and shipped at install
# (nixos-anywhere --extra-files -> /etc/ssh/ssh_host_ed25519_key).
# samba + pass-broker secrets are declared in profiles/workstation.nix.
{
sops.defaultSopsFile = ../../secrets/terra.yaml;
sops.age.sshKeyPaths = [ "/etc/ssh/ssh_host_ed25519_key" ];
@@ -13,20 +14,6 @@
sops.secrets.darman_password.neededForUsers = true;
users.users.darman.hashedPasswordFile = config.sops.secrets.darman_password.path;
# Credentials file for the //jupiter/data cifs mount (see configuration.nix).
# samba_password mirrors jupiter's own samba_password secret (services/network/samba.nix) —
# same value, just also encrypted to terra so it can authenticate as the same smb user.
sops.secrets.samba_password = { };
sops.templates."jupiter-smb.credentials".content = ''
username=darman
password=${config.sops.placeholder.samba_password}
'';
# LibreChat's CREDS_KEY/IV encrypt stored user credentials (linked 3rd-party
# API keys etc) at rest in mongo; JWT_SECRET/JWT_REFRESH_SECRET sign session
# tokens. All four are random, generated once with `sops --set` (see
# CLAUDE.md) — losing/rotating them just invalidates existing sessions and
# any saved per-user API keys, nothing else depends on their value.
# luna-voiced (services/desktop/luna-voice.nix) runs as a USER service, so
# these cannot stay root:root 0400 — a user manager cannot read them and
# LoadCredential does not bridge that gap either. Hence owner, not mode.
@@ -38,16 +25,4 @@
# files; see CLAUDE.md.
sops.secrets.hermes_api_server_key.owner = "darman";
sops.secrets.elevenlabs_api_key.owner = "darman";
# pass-broker (services/identity/pass-broker.nix): the agent PAT and its
# dedicated Telegram bot. Owner pass-broker, so darman cannot read them.
sops.secrets.pass_broker_pat.owner = "pass-broker";
sops.secrets.pass_broker_telegram_token.owner = "pass-broker";
# Not broker-specific; a second reader needs a sops.templates copy, not a new owner.
sops.secrets.darman_telegram_user_id.owner = "pass-broker";
sops.secrets.librechat_creds_key = { };
sops.secrets.librechat_creds_iv = { };
sops.secrets.librechat_jwt_secret = { };
sops.secrets.librechat_jwt_refresh_secret = { };
}