The owner's operating manual

Runbook / How to Use

How to use this documentation

  1. Start here — this page. It tells you what exists and what to type.
  2. System Audit — the machine's as-found state, before any of this work. If something surprises you, compare against the audit.
  3. Change Log — everything that was done, newest first, each entry with why and a revert procedure. This is the receipt page: if you want to undo or tweak anything, start there.
  4. Architecture / Models / Benchmarks — the design, the picks and their trade-offs, and the measured numbers with reproduction commands.
  5. Anything the setup work does from now on lands in the change log the same day. The site is rebuilt and redeployed on every update.

Getting in

ssh wg@frame-serv-2          # from any device on the tailnet (MagicDNS)
ssh [email protected]        # same node, by IP

An admin SSH key (from the operator's machine, dxverm@ashborn) is installed for wg. Your own password still works. wg has full sudo (wheel); the inference tree /srv/llm is owned by wg.

What's where

/srv/llm/src/llama.cpp/          inference engine source + builds (vulkan/, hip/)
/srv/llm/models/                 model weights (2TB NVMe, ext4, "LLM-MODELS" label)
/srv/llm/venv/                   python env with the hf CLI (model downloads)
/etc/sudoers.d/dan.bak-20260909-orig   original sudoers fragment (pre-fix)

Daily operations (once serving is live — commands will be finalized)

Being built now; the exact unit names and commands will be recorded here as they ship, and each new service gets its own change-log entry.

Adding a new model

export HF_HUB_ENABLE_HF_TRANSFER=1
/srv/llm/venv/bin/hf download / [file.gguf ...] \
  --local-dir /srv/llm/models/

Then register it in the llama-swap config (Architecture page) and reload.

If something breaks