Files
esh-pfi-infrastructure/services/albok-nemi/albok-nemi.service
T

23 lines
1.1 KiB
Desktop File

# Nemi: walks albok's three-wing manifest (fleet/memory, fleet/stash, personal/agent-feedback) into
# albok-service on nh3-docker. Code and config belong to albok-dev (vh/albok, packages/albok-nemi);
# this unit and its timer belong to infra-ops. Installed 2026-10-03 at albok-dev's request (thread
# 01M40JGV4BEVXC9NQVTPX82BV8). See README.md beside this file.
#
# ⚠ Two walks must never overlap on one wing (each run tombstones what the other did not send). A
# oneshot behind a timer gives that: the timer never starts the unit while it is active. Start a
# manual walk with `systemctl --user start albok-nemi.service`, not a bare `uv run nemi run`.
# Exit 1 = a wing failed (cause in the report), 2 = service unreachable; both trip OnFailure.
[Unit]
Description=Nemi walk: albok manifest -> albok-service (albok-dev)
Documentation=file:///home/lkraven/development/eshpfi-management/services/albok-nemi/README.md
[Service]
Type=oneshot
WorkingDirectory=/home/lkraven/development/albok
Environment=NEMI_CONFIG=/home/lkraven/.config/albok/nemi.yaml
ExecStart=/home/lkraven/bin/uv run nemi run
TimeoutStartSec=2h
Nice=10
IOSchedulingClass=best-effort
IOSchedulingPriority=7