Files
esh-pfi-infrastructure/configs/svos-apps/nh3-dev/svos-terminal.service
T
vh 3c92a1281e fix(svos-apps): svos-terminal unit reaches zellij (~/.cargo/bin on PATH); app-terminal up after 2 days degraded
A user unit's default PATH lacks ~/.cargo/bin, so every zellij call from
app-terminal failed to launch (rc 127 under the unit's environment), and the app
reported degraded from the U13 cutover on. With PATH set, the kernel logged
app-terminal up at 15:56:40Z; the pinned manifest is unchanged and no card was
raised.
2026-10-13 08:57:10 -07:00

25 lines
1.3 KiB
Desktop File

# eshpfi configs/svos-apps/nh3-dev/ (infra-ops, U13 2026-10-11): app-terminal as a USER unit of lkraven on nh3-dev.
# It must be a user unit: its seat launcher runs `systemctl --user start zellij-fleet@Claude` and never parents the
# zellij server. The kernel reaches it through https://svos-seathost.nh3.phasefinal.com (fleet Caddy -> :8404).
# Config /var/lib/svos/config/apps/terminal.toml; credential /etc/svos/env/terminal.env (vault nh3-svos/svos-terminal-credential).
[Unit]
Description=SVOS Terminal connector + seat host (app-terminal, U8/U5b)
ConditionPathExists=/etc/svos/env/terminal.env
[Service]
Type=simple
UMask=0077
Restart=on-failure
RestartSec=3
TimeoutStopSec=20
WorkingDirectory=/var/lib/svos
EnvironmentFile=/etc/svos/env/terminal.env
Environment=SVOS_KERNEL_URL=https://svos-kernel.phasefinal.com
Environment=SVOS_DATA_ROOT=/var/lib/svos
Environment=SVOS_APP_LISTEN=127.0.0.1:8404
# zellij is lkraven's cargo install (~/.cargo/bin), which a user unit's default PATH does not reach. Without it every
# `zellij` call fails to launch: /health stays "degraded" and dump/inject cannot run (found 2026-10-13, svos-dev's report).
Environment=PATH=/home/lkraven/.cargo/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
ExecStart=/opt/svos/current/apps-env/bin/svos-terminal
[Install]
WantedBy=default.target