Getting Started & Conventions

Welcome. This vault documents the Sportstlm production VPS (and its pipelines).
Everything here was generated from the live box via ssh sportstlm-vps, not from memory.

How this vault is organized

• Home — the map of content (MOC). Start there.
• VPS/ — the box itself: routing, containers, timers, supervision, backups, secrets, sync.
• Sportstlm/ — the main hub and its data/LLM pipelines.

Notes are linked with Obsidian <span style="color:var(--muted)">wikilinks (unresolved)</span>. Open the graph view to see the network.

Conventions

1. Facts over memory. Every note is re-derivable from the live box. When in doubt,
   re-run the SSH discovery rather than trusting a stale note.
2. Secrets are locations-only. No password, token, or key value is ever written here —
   only where they live (see VPS/Credentials). Never paste a secret into a note.
3. Dates. Each snapshot is tagged with a Last mapped date. The auto-refresh job
   bumps it.
4. Authority. VPS/Runbook is the verbatim import of /opt/RUNBOOK.md — the
   on-box source of truth. Structured notes are derived from it. When they disagree,
   the runbook (or the live box) wins.
5. Editing. Prefer targeted edits over rewriting whole notes; preserve headings and
   wikilinks so the graph stays intact.

Maintenance (auto-refresh)

A weekly cron job re-snapshots the VPS and refreshes stale facts (container statuses,
timer list, registry count, uptime/disk, Last mapped date). It does not rewrite
prose or touch secrets. If you notice drift, the manual recipe is:

ssh sportstlm-vps   # then run the discovery commands in Home.md's "Quick facts"

Quick SSH

ssh sportstlm-vps   # Host alias → root@201.18.219.127, key ~/.ssh/sportstlm_vps