dank/command-center
1
0
Fork 0
Code Issues 5 Pull Requests Actions Packages Projects Releases Wiki Activity

Merge pull request 'Docs: full truth audit - statusline page + system/gitea pages realigned' (#7) from chore/docs-statusline-audit into main

Browse Source
This commit was merged in pull request #7.
This commit is contained in:
dank
2026-10-18 13:10:48 -07:00
parent 59a89553b7 ae82aa00e4
commit e5d00fd91f
13 changed files with 309 additions and 179 deletions
Download Patch File Download Diff File Expand all files Collapse all files
AGENTS.md
+6 -5
View File
@@ -71,8 +71,8 @@ secret in every agent's context window on every machine that pulls this repo.
| box | role | GPU | notes | | box | role | GPU | notes |
|-----|------|-----|-------| |-----|------|-----|-------|
| Dev workstation | client box, never runs inference | laptop iGPU + dGPU (non-unified) | mainline llama.cpp at `~/GitPackages/llama.cpp/build/bin/`; this repo lives here at `~/.omp` | | Dev workstation | client box, never runs inference | laptop iGPU + dGPU (non-unified) | mainline llama.cpp at `~/GitPackages/llama.cpp/build/bin/`; this repo lives here at `~/.omp` |
| Dankclaw | bench target, runs the large serving model | Strix Halo APU — **unified memory** | ROCmFPX fork at `~/GitPackages/ROCmFPX/build-qwen38/bin/`; prod service `frank-default-large`, port 7770; ssh: `ssh dankclaw` | | Dankclaw | bench target, secondary models + service stack | Strix Halo APU (**unified memory**) + RTX 3090 (moved over from Dankserver 2026-09) | prod services `frank-dragoon` (halogen-flash-server, :7770, iGPU) and `frank-zealot` (llama.cpp PrismML fork, :7771, 3090); runbooks in the serverAppConfigs vault (`~/Projects/serverAppConfig/serverAppConfigs-docs/LLM/`); ssh: `ssh dankclaw` |
| Dankserver | FreeToken box | RTX 3090 dGPU — non-unified | runs `frank-default-small`; ssh: `ssh dankserver` | | Dankserver | main-model box | 2× Radeon AI PRO R9700 — non-unified (was RTX 3090 until 2026-09) | runs `frank-archon` (radiance, TP=2, :7770) — **this repo's operator session runs on it**; ssh: `ssh dankserver` |
## Environment gotchas ## Environment gotchas
@@ -84,9 +84,10 @@ secret in every agent's context window on every machine that pulls this repo.
- SSH into both servers is BatchMode-capable from here: - SSH into both servers is BatchMode-capable from here:
`ssh -o BatchMode=yes dankclaw '<read-only command>'` — read-only probes are `ssh -o BatchMode=yes dankclaw '<read-only command>'` — read-only probes are
always allowed; state changes on remote boxes are not, without a per-run OK. always allowed; state changes on remote boxes are not, without a per-run OK.
- `frank-default-large` on Dankclaw is a **production service** shared with this - `frank-archon` (Dankserver), `frank-dragoon`, and `frank-zealot` (Dankclaw)
repo's operator: never stop, mask, or restart it (or any production service on are **production services** shared with this repo's operator: never stop,
any box) without an explicit, current, per-run OK from Frank. mask, or restart them (or any production service on any box) without an
explicit, current, per-run OK from Frank.
## File-organization doctrine (why this repo stays readable) ## File-organization doctrine (why this repo stays readable)
omp-docs/core/index.md
+8 -2
View File
@@ -1,12 +1,18 @@
# Core Documentation # Core Documentation
These files define the structural conventions that govern the pi agent system itself. They are the grammar rules — boring until you break them, then devastating. These files define the structural conventions that govern the agent system itself. They are the grammar rules — boring until you break them, then devastating.
> **Archive note (2026-10-18).** The settings pages (`settings.md`, `settings.json`)
> capture the retired **pi** harness configuration (`frank-default-*` endpoints,
> RTX 3090-era hardware) and are historical records. The live config is
> `agent/config.yml` + `agent/models.yml` in this repo; current fleet endpoints
> are on [System hosts](/system/index.md). The AGENTS.md format pages remain current.
## Concept Files ## Concept Files
* [AGENTS.md Format Specification](agents-md-format.md) — Canonical structure and conventions for the system-level instruction file that governs agent behavior. * [AGENTS.md Format Specification](agents-md-format.md) — Canonical structure and conventions for the system-level instruction file that governs agent behavior.
* [AGENTS.md Index](index-doc.md) — Overview of the cached tool documentation system and how to add new entries. * [AGENTS.md Index](index-doc.md) — Overview of the cached tool documentation system and how to add new entries.
* [Pi Settings System](settings.md) — Current system configuration: providers, models, packages, subagent overrides, and runtime options. * [Pi Settings System](settings.md) — pi-era `settings.json` record (archive): providers, models, packages, subagent overrides.
## Change Tracking ## Change Tracking
omp-docs/log.md
+17 -1
View File
@@ -11,11 +11,27 @@ timestamp: 2026-08-28
# Bundle Change Log # Bundle Change Log
## 2026-10-18 — Sibling-vault overlap census; system docs realigned to live ground truth
Census of `omp-docs/` against `~/Projects/serverAppConfig/serverAppConfigs-docs/` (subagent + live-ssh verification) found four contradicting pairs; all OURS-side stale pages corrected, THEIRS side flagged only (their repo, their PR flow). Ground truth from read-only probes on both boxes 2026-10-18.
* **Hardware drift corrected** (`system/dankserver.md`, `system/dankclaw.md` rewritten, `AGENTS.md` machine table): RTX 3090 moved Dankserver→Dankclaw 2026-09; dankserver now 2× Radeon AI PRO R9700 (7700X stays — the "board swap" story is false), 246 GiB RAM, no swap; dankclaw 121 GiB RAM + 64 GiB swap. Served models per live units: frank-archon (:7770 dankserver, radiance TP=2 iq4r), frank-dragoon (:7770 dankclaw, halogen NATIVE v2, iGPU), frank-zealot (:7771 dankclaw, llama.cpp PrismML, Ternary-Bonsai-2-27B PQ2_0, 3090). Both kernels 7.0.0-38-generic; dankclaw :7770 needs no auth.
* **Gitea pages corrected** (`tools/gitea/` index + 3 subpages): `gitea-caddy` quadlet retired — fleet Caddy fronts the domain; data tree is `/home/dank/Containers/gitea/{data,postgres,env}` (2026-09-01 standard), `/opt/gitea/` is a do-not-use leftover; LAN IP, live domain, no WAN address.
* **Pi-era pages demarcated as archive** (`pi/index.md`, `core/index.md` banners; `core/index.md` said settings.md was "Current"): `frank-default-small/large` endpoints, role tables, and 3090/4070 hardware rows now read as pi-era records. `tools/llama-cpp/index.md` fleet note modernized to the one remaining llama.cpp endpoint (zealot :7771).
* **Their-side staleness flagged, NOT edited** (for operator clarification): `Agent/OMP Harness.md` still says thresholdPercent 70 — live config is **95** (`agent/config.yml:84`); `index.md:18` says Dankserver Ubuntu 24.04 vs their own specs page 26.04; `Dankclaw/Stack.md` "current mapping (2026-09-03)" predates the ACTIVE dragoon/zealot runbooks it links beside; `index.md:548` links the superseded pi-era KB at `~/.pi/agent/docs/`.
* Consistent duplicates (no action): niri/noctalia desktop pages, Caddy reference. Divergence clarified: their "composer" = OpenWebUI chat box; ours = omp composer shape — unrelated subjects.
## 2026-10-18 — Status line docs truth audit (full-source re-verification)
Exhaustive claim-by-claim re-audit of [OMP Status Line Customization](/pi/statusline.md) against the minified `dist/cli.js` bundle plus a live screenshot matrix (band × {off, percentage, embedded}, claude × off). Page carries an **Audit log** section; four first-pass claims were false and are corrected (see there): claude's rule is *not* the context meter (meter is `box`/`band` only; the "red rule" was the session-accent filler), the "Tern-only" composer-bar claim was bogus (the readout is `composer.tokenRate`, default off), `segmentOptions` are **not** gated to `preset: custom` (only the segment arrays are), and the `mode` segment's states are Plan/Prewalk/Goal/Vibe/Loop (no yolo). Page expanded with: the 7-preset defaults table, per-shape `statusAttachment`/`bottomBar` model (8 built-ins + plugin shape registry), `contextLine` per-value behavior, the 27-segment catalog with triggers/options, `segmentOptions` schema, and the full `statusLine.*`/`composer.*` knob registry. The bundle's own "(box composer only)" knob description for `contextLine` is upstream-wrong — band honors it.
ServerAppConfigs-docs overlap census: flagged separately for the operator (morning report); no doc merged/changed on either side.
## 2026-10-18 — Status line rebuilt on custom segments; frank-archon display name slimmed ## 2026-10-18 — Status line rebuilt on custom segments; frank-archon display name slimmed
Interactive tune-up of the omp status bar (grilling session, live loop: config edit → watcher repaint → niri screenshot verify). New knowledge page: [OMP Status Line Customization](/pi/statusline.md). Interactive tune-up of the omp status bar (grilling session, live loop: config edit → watcher repaint → niri screenshot verify). New knowledge page: [OMP Status Line Customization](/pi/statusline.md).
* **Mechanics discovered:** `leftSegments`/`rightSegments` are inert unless `preset: custom` (fleet was on `nerd` with dead arrays); `composer.shape` routes them — `band` merges both arrays into one row above the editor (title rides the working row), `claude` splits them into top chip + bottom strip. The `claude` red rule **is** the context meter (length = usage); `contextLine` label variants render in `box`/`band` — `band` paints the labeled inline meter (`60% ——— × 200K`). Working row (`⠿ Working… + tok/s`) is hardcoded — model/thinking can never join it (Tern-only). Eight composer shapes registered in the bundle. * **Mechanics discovered:** `leftSegments`/`rightSegments` are inert unless `preset: custom` (fleet was on `nerd` with dead arrays; `segmentOptions` *do* merge under named presets); `composer.shape` routes them — `band` merges both arrays into one row above the editor (title rides the working row), `claude` splits them into top chip + bottom strip. The context meter exists **only in `box`/`band`** — `contextLine`: `off` plain rule, `embedded` hoists the context segment into the labeled inline meter (`60% ——— × 200K`), `percentage`/`annotated` paint an unlabeled proportional rule meter (all four live-verified); every other shape's rule is a constant session-accent filler. Working row (session title + tok/s readout gated by `composer.tokenRate`, default off) is composer chrome — model/thinking can never join it. Eight composer shapes ship in the bundle; plugins can register more.
* **Final bar (`band`, after a `claude` sojourn):** left = `session_name · vim · mode · hostname · path · git(no branch text) · pr`; right cluster in array order = `model · cost · time_spent` (`context_pct` hoists out of the run to paint the labeled inline meter `60% ——— × 200K` as a flexible spacer between the groups). Cut: tok/s duplicate, clock, cache trio, `context_total`, `subagents`, `session` hash, and `token_in`/`token_out` (cumulative totals live in `/session`). `path`: logical `project/worktree` label (`stripWorkPrefix: true`, kept after a live `false` trial of the full cwd); branch text dropped (worktree branches are autogenerated), dirty badges kept. * **Final bar (`band`, after a `claude` sojourn):** left = `session_name · vim · mode · hostname · path · git(no branch text) · pr`; right cluster in array order = `model · cost · time_spent` (`context_pct` hoists out of the run to paint the labeled inline meter `60% ——— × 200K` as a flexible spacer between the groups). Cut: tok/s duplicate, clock, cache trio, `context_total`, `subagents`, `session` hash, and `token_in`/`token_out` (cumulative totals live in `/session`). `path`: logical `project/worktree` label (`stripWorkPrefix: true`, kept after a live `false` trial of the full cwd); branch text dropped (worktree branches are autogenerated), dirty badges kept.
* **models.yml:** frank-archon display `name` slimmed to `"frank-archon"` (endpoint suffix dropped; `id` untouched). * **models.yml:** frank-archon display `name` slimmed to `"frank-archon"` (endpoint suffix dropped; `id` untouched).
* **Out of scope noted:** worktree name generation (`wt-<date>-<hash>`) is omp-internal; possible upstream feature request. * **Out of scope noted:** worktree name generation (`wt-<date>-<hash>`) is omp-internal; possible upstream feature request.
omp-docs/pi/index.md
+7 -3
View File
@@ -1,8 +1,12 @@
# Pi Configuration # Pi Configuration
Documentation for the pi coding agent installation on ](../system/index.md). > **Archive note (2026-10-18).** Most pages in this directory document the retired
Everything here is configured locally on the workstation; the LLM providers are the > **pi** harness (settings.json / models.json, `frank-default-*` endpoints, verified
two llama.cpp servers (Dankserver, Dankclaw). > 2026-08-28). The live harness is **omp** — its config is `agent/config.yml` +
> `agent/models.yml` in this repo, the current fleet endpoints are on
> [System hosts](/system/index.md), and omp-specific knowledge lands in pages like
> [OMP Status Line Customization](/pi/statusline.md) below. Read pi pages as
> historical records, not current state.
## Configuration Files ## Configuration Files
omp-docs/pi/statusline.md
+151 -55
View File
@@ -1,7 +1,7 @@
--- ---
type: reference type: reference
title: OMP Status Line Customization title: OMP Status Line Customization
description: How the omp status line actually works — presets vs custom arrays, composer-shape segment routing, the context meter, and the fleet's tuned segment layout. description: How the omp status line actually works — presets vs custom arrays, composer-shape segment routing, the context meter (box/band only), the 27-segment catalog, and the fleet's tuned layout.
tags: tags:
- omp - omp
- tui - tui
@@ -12,36 +12,89 @@ timestamp: 2026-10-18
# OMP Status Line Customization # OMP Status Line Customization
Ground truth from the installed bundle (`@oh-my-pi/pi-coding-agent/dist/cli.js`) Ground truth from the installed bundle (`@oh-my-pi/pi-coding-agent/dist/cli.js`),
verified live on blankpad 2026-10-18. All knobs live in verified live on blankpad 2026-10-18 and re-audited line-by-line against the
`agent/config.yml` under `statusLine:` (tracked — see minified source the same day (see [Audit log](#audit-log)). Status knobs live
[Command Center repo](../core/index.md)); the file is file-watched, so edits in `agent/config.yml` under `statusLine:`; the two composer knobs
repaint a running session without restart (verify visually: niri screenshot, (`composer.shape`, `composer.tokenRate`) under `composer:`. The file is
see [niri capture recipe](../system/index.md)). file-watched — edits repaint a running session without restart (verify
visually: niri screenshot, see [niri capture recipe](../system/index.md)).
`/settings` (Appearance tab) previews these live with sample data.
## Preset vs custom — the trap ## Preset vs custom — the trap
`statusLine.preset` ships whole configurations (`default`, `minimal`, `statusLine.preset` ships whole configurations. **`leftSegments` /
`compact`, `full`, `nerd`, `ascii`, `custom`). **`leftSegments` / `rightSegments` are ignored unless `preset: custom`** (`s ? user ?? preset
`rightSegments` / `segmentOptions` are only read when `preset: custom`** — : preset` in the resolver). **`segmentOptions` is NOT gated** — user options
with any named preset they are silently ignored. The fleet config runs merge over the preset's own options under *every* preset.
`preset: custom`.
| preset | leftSegments | rightSegments | separator |
|---|---|---|---|
| `default` | pi vim model mode collab stream path git pr context_pct cost | session_name | powerline-thin |
| `minimal` | vim path git | session_name mode context_pct | slash |
| `compact` | vim model mode git pr | session_name cost context_pct | powerline-thin |
| `full` | pi vim hostname model mode path git pr subagents | session_name cache_hit token_in token_out token_rate cache_read cost context_pct time_spent time | powerline |
| `nerd` | pi vim hostname model mode path git pr session subagents | session_name token_in token_out cache_read cache_write token_rate cost context_pct context_total time_spent time | powerline |
| `ascii` | vim model mode path git pr | session_name token_total cost context_pct | ascii |
| `custom` | your `statusLine.leftSegments` | your `statusLine.rightSegments` | powerline-thin |
The built-in default for `statusLine.leftSegments`/`rightSegments` themselves
is the `ascii`-era pair (`vim model mode path git pr` / `session_name
token_total cost context_pct`) — a config carrying those arrays with a named
preset is running the preset, not the arrays. The fleet runs `preset: custom`.
## Composer shape routes the segments ## Composer shape routes the segments
`composer.shape` decides *where* the two segment arrays render: `composer.shape` decides *where* the two arrays render. Eight shapes ship in
the bundle; the plugin API can register more (`zG()` = built-ins + a live
registration map). Internally each shape carries `statusAttachment`,
`bottomBar`, `bottomBarGap`:
| shape | leftSegments | rightSegments | | shape | attach | bottom bar | leftSegments | rightSegments |
|---|---|---| |---|---|---|---|---|
| `band` (fleet) | merged single row above editor | same row, right side (title skipped — it rides the working row) | | `band` (fleet, default) | top-band | none | merged single row above editor, left | same row, right (`session_name` skipped — title rides the working row) |
| `claude` | bottom strip, left-aligned | top rule chip, right-aligned | | `box` | top-border | none | box top border | box top border |
| `rule` | same as claude, gap above strip | same | | `claude` | top-rule-chip | left | bottom strip, left | top rule chip, right-aligned |
| `box` | box top border | box top border | | `rule` | top-rule-chip | left + gap | like claude, gap above strip | like claude |
| `borderless` / `pi` / `field` / `rail` | single bottom bar | single bottom bar | | `pi` | none | full | single bottom bar | single bottom bar |
| `borderless` | none | full | single bottom bar | single bottom bar |
| `field` / `rail` | none | full + gap (filled surface) | single bottom bar | single bottom bar |
The `⠿ Working…` row is hardcoded: shimmer text + `composer.tokenRate` readout The chip/strip layouts paint their rules as **session-accent fillers, not
(+ session title in `band` only). Model/thinking-level can never join it meters** — the context meter exists only in `box` and `band`
despite the settings description — that composer-bar behavior is Tern-only. (see next section). The top-rule chip renders right segments only, the bottom
strip left segments only.
The working row is composer chrome, not segment-addressable: session title +
shimmer, plus the tok/s readout when `composer.tokenRate: true` (default
false). The readout is estimated from streamed deltas, corrected by billed
output counts; the bundle also mentions a native-composer-bar placement in
filled styles.
## The context meter
`statusLine.contextLine` (enum `off` / `percentage` / `annotated` /
`embedded`, default `embedded`) tunes the rule between the segment groups.
The knob description says "box composer only" — **that is wrong**: the meter
renders in `box` **and** `band`; in every other shape the rule is a constant
session-accent filler regardless of this setting (live-verified claude with
`off` vs `embedded`: identical, and not context-proportional).
In box/band:
- `off` → plain accent rule (single color, full width).
- `embedded` → the inline labeled meter: `60% ——— × 200K`. Requires
`contextWindow > 0`, a `context_pct`/`context_total` segment present in
either array, and at least one non-context segment. The context segment(s)
are **hoisted out of the arrays** — they never render as text in this mode.
- `percentage` / `annotated` → unlabeled proportional meter painted into the
rule (live-verified in band: colored fill ∝ usage at the rule's right end);
`context_pct` stays a normal text segment.
Fill length ∝ `min(100, contextPercent)`; >100% paints the raw percent and
shortens the meter. Meter/segment color thresholds scale with window size —
warning at ≥ min(50 %, 150K tokens), purple ≥ min(70 %, 270K), error ≥
min(90 %, 500K); below that the theme's `statusLineContext` color.
## Segment universe (27) ## Segment universe (27)
@@ -50,22 +103,33 @@ despite the settings description — that composer-bar behavior is Tern-only.
`context_total`, `time_spent`, `time`, `session`, `hostname`, `cache_read`, `context_total`, `time_spent`, `time`, `session`, `hostname`, `cache_read`,
`cache_write`, `cache_hit`, `session_name`, `usage`, `collab`, `stream`, `vim`. `cache_write`, `cache_hit`, `session_name`, `usage`, `collab`, `stream`, `vim`.
Conditional segments render nothing until their trigger exists: `vim` needs Zero/inactive segments render nothing — dead weight costs no width.
`tui.vimMode`, `mode` needs plan/yolo, `pr` needs an associated PR, `git` shows
staged/unstaged/untracked badges (branch text optional via
`segmentOptions.git.showBranch`), `status` needs an extension push.
`session` = first 8 chars of the session id (resume-by-id handle).
## The context meter | segment | renders | trigger / notes |
|---|---|---|
In the `band` shape (fleet) the meter is the labeled inline line between the | `pi` | brand glyph + turn-elapsed | while streaming; focused-agent ghost id (warning color) when a subagent is focused |
segment groups (`60% ———— × 200K`). In the `claude` shape the red rule left of | `status` | hook/extension statuses, dot-joined | extension pushes via `ctx.ui.setStatus()` (ordered by key); suppressed in footer when `statusLine.showHookStatus: false` |
the right-segment chip **is** the meter: its length tracks context usage. | `model` | display `name` + thinking level | suffix hidden by `segmentOptions.model.showThinkingLevel: false`; `statusLine.compactThinkingLevel: true` (default) swaps in a compact glyph; fast-mode, advisor/tariff badges attach here |
`statusLine.contextLine` (`off` / `percentage` / `annotated` / `embedded`) | `mode` | `Plan` / `Prewalk` / `Goal` / `Vibe` / `Loop …` | only in those modes (paused variants add a pause glyph); there is **no yolo/auto-approval display** in this segment |
only changes rendering in `box`/`band` — in `claude` all non-`off` values | `path` | cwd or `project/worktree` label | see [Path segment](#path-segment-and-stripworkprefix) |
look identical. Docs' claim that contextLine is "box composer only" is | `git` | branch + dirty badges | `+N` staged, `*N` unstaged, `?N` untracked (`segmentOptions.git.showStaged/showUnstaged/showUntracked`, default true); `showBranch: false` hides branch text and keeps badges (git icon carries them); color flips on dirty |
wrong for the meter itself; the labeled inline variant is the box/band-only | `pr` | `#<number>` hyperlink | only once the session has an associated PR |
part. | `subagents` | count | hidden at 0; when subagents are actively running the composer paints its own live badge and this segment self-suppresses |
| `token_in` / `token_out` | cumulative session input/output tokens | hidden at 0; `cache_read` / `cache_write` likewise cumulative |
| `token_total` | `input + output + cache_write + orchestration_in + orchestration_out` | hidden at 0 |
| `token_rate` | `N.N tok/s` | hidden when not streaming (the working-row readout is a separate, `composer.tokenRate`-gated thing) |
| `cost` | session cost | includes subagent-tree + advisor cost; `↑`/`↓` peak/off-peak arrow for time-priced providers |
| `context_pct` | `NN.N%/200K` (or window alone when percent is unknown) | hoisted into the meter in `embedded` box/band; auto-compact speculation icon rides along |
| `context_total` | absolute context tokens | also hoisted by the embedded meter |
| `time_spent` | active session time | hidden under 1 s; this is *active* time, not wall clock |
| `time` | wall clock | `segmentOptions.time.format: "12h"/"24h"`, `showSeconds` |
| `session` | first 8 chars of session id (`new` before resume exists) | resume-by-id handle |
| `session_name` | session title, accent | in `band` it renders on the working row instead |
| `hostname` | short hostname | accent-tinted with session color |
| `usage` | rate-limit windows | 5h / daily / 7d / monthly bars + tier badge, when the provider reports them |
| `collab` | `collab:N` / `collab guest:N` | only in collab sessions |
| `stream` | `● LIVE <viewers>` / `● REC` | only while streaming/recording |
| `vim` | mode glyph/word | only while vim keybindings are active; selected-line count appended (` 3L`); `display` icon vs text comes from the vim runtime, not config |
## Path segment and `stripWorkPrefix` ## Path segment and `stripWorkPrefix`
@@ -81,23 +145,55 @@ part.
2. **All sessions:** `true` uses the pretty display path (scratch sessions 2. **All sessions:** `true` uses the pretty display path (scratch sessions
get the scratch-folder icon); `false` uses the raw absolute cwd. get the scratch-folder icon); `false` uses the raw absolute cwd.
`abbreviate` and `maxLength` (clip, default 40) apply afterwards in both `abbreviate` (default **true**: home → `~`; `false` keeps the full path —
modes. The fleet runs `true` — logical label, worktree glyph (verified live also affects tool labels/errors per upstream docs) and `maxLength` (clip,
2026-10-18; an earlier trial of `false` for the full cwd was rejected by eye). default 40) apply afterwards in both modes. The fleet runs `true` — logical
label, worktree glyph (verified live 2026-10-18; an earlier trial of `false`
for the full cwd was rejected by eye).
## Status knobs (registry-verified)
`statusLine.preset` · `.leftSegments` · `.rightSegments` · `.segmentOptions` ·
`.separator` (`powerline` `powerline-thin` `slash` `pipe` `block` `none`
`ascii`; default `powerline-thin`) · `.contextLine` · `.sessionAccent`
(default true; hashes the session name into the editor border *and* the
accent-tinted segments/meter color) · `.transparent` (terminal background,
no status bg fill) · `.showHookStatus` · `.compactThinkingLevel` (default
true). Plus `symbolPreset` at top level (`unicode` `nerd` `ascii` — segment
glyphs follow it).
## Fleet configuration (2026-10-18) ## Fleet configuration (2026-10-18)
- Shape `band`: one merged status row. Left group: `session_name`, `vim`, - Shape `band`: one merged status row. Left group: `session_name`→working
`mode`, `hostname`, `path`, `git` (no branch text — worktree branches are row (skipped), `vim`, `mode`, `hostname`, `path`, `git` (no branch text —
autogenerated names), `pr`. Right group (array order = paint order, so the worktree branches are autogenerated names), `pr`. Right group (array order
last entry hugs the screen edge): `model`, `cost`, `context_pct`, = paint order, so the last entry hugs the screen edge): `model`, `cost`,
`time_spent` — `context_pct` hoists out of the run to paint the labeled `context_pct`, `time_spent` — `context_pct` hoists out of the run to paint
inline meter (`60% ——— × 200K`) as a flexible spacer between the groups. the labeled inline meter (`60% ——— × 200K`) between the groups under
`session_name` renders on the working row, not the status row. `contextLine: embedded`.
- Deliberately cut: `token_rate` (lives on the working row), `time` (panel - Deliberately cut: `token_rate` (working-row readout covers it), `time`
clock), `cache_*` (noise), `context_total` (implied by the meter), (panel clock), `cache_*` (noise), `context_total` (implied by the meter),
`subagents`, `session`, `token_in`/`token_out` (cumulative totals are `subagents` (live badge supersedes it), `session`, `token_in`/`token_out`
in `/session` anyway). (cumulative totals are in `/session` anyway).
- Model display names slimmed in `models.yml` (`frank-archon`, no endpoint - `models.yml`: frank-archon's display `name` slimmed to `"frank-archon"`
suffix); `name:` is free-form display, `id:` is the wiring — renaming ids is (endpoint suffix dropped); frank-dragoon/frank-zealot keep their endpoint
the cutover procedure, see [Pi Models](/pi/models.md). suffixes. `name:` is free-form display, `id:` is the wiring — renaming ids
is the cutover procedure, see [Pi Models](/pi/models.md).
## Audit log
2026-10-18 full-source re-audit corrected the first pass of this page:
- ~~claude shape's top rule is the context meter~~ — **false**. The
meter code path runs only for `box`/`band`; claude/rule/pi/borderless/
field/rail rules are constant session-accent fillers. (Earlier reading
mistook the accent rule for a meter.)
- ~~working-row composer-bar variant is "Tern-only"~~ — **false**; the
tok/s readout is the `composer.tokenRate` option (default false), title
placement is composer chrome.
- ~~`segmentOptions` gated to `preset: custom`~~ — **false**; options merge
under every preset, only the segment *arrays* are gated.
- ~~`mode` covers yolo~~ — **false**; states are Plan/Prewalk/Goal/Vibe/Loop.
- `contextLine` "(box composer only)" — the *bundle description* is wrong;
band honors it too (verified live: `off` plain rule, `percentage` rule
meter, `embedded` inline meter, screenshots + code).
omp-docs/system/dankclaw.md
+45 -49
View File
@@ -1,83 +1,79 @@
--- ---
type: reference type: reference
title: Dankclaw title: Dankclaw
description: Secondary inference server at 192.168.0.143. Runs llama.cpp (frank-default-large). description: Inference and services box at 192.168.0.143 — frank-dragoon (halogen-flash-server, Strix Halo iGPU, :7770) and frank-zealot (llama.cpp on the RTX 3090, :7771), plus Gitea/Caddy/OpenWebUI services.
tags: tags:
- network - network
- llamacpp - llamacpp
- inference - inference
- server - server
- comfyui - comfyui
- unverified
generated: generated:
by: chief-designer/agent by: chief-designer/agent
at: 2026-08-26T00:00:00Z at: 2026-08-26T00:00:00Z
verified: 2026-08-28 verified: 2026-10-18
--- ---
# Dankclaw # Dankclaw
Secondary llama.cpp inference server for the Frank Program. Serves larger models used by planner, worker, reviewer, oracle, and context-builder subagents. Strix Halo mini-PC carrying the fleet's secondary models and most of the
service stack (Gitea, Caddy, OpenWebUI, SearXNG). Two GPU-class devices: the
Radeon 8060S iGPU with 119 GiB unified memory, and the RTX 3090 moved over
from Dankserver in September 2026.
## Connection Details ## Connection Details
| Property | Value | | Property | Value |
|----------|-------| |----------|-------|
| **Hostname** | dankclaw | | **Hostname** | dankclaw |
| **IP Address** | 192.168.0.143 | | **IP Address** | 192.168.0.143 (LAN) |
| **Port** | 7770 | | **Auth** | none required on :7770 (verified 2026-10-18) |
| **Base URL** | `http://192.168.0.143:7770/v1` |
| **API** | OpenAI-compatible completions |
| **Authentication** | API key configured |
## Models ## Inference Services
| Model ID | Context Window | Reasoning | Input Types | | Model ID | Unit | Endpoint | Engine / weights |
|----------|---------------|-----------|-------------| |----------|------|----------|------------------|
| `frank-default-large` | 262,144 tokens | Yes | Text, *Image* (unverified) | | `frank-dragoon` | `frank-dragoon.service` (root) | `:7770` | halogen-flash-server container — Quat3rnion NATIVE v2 abliterated Qwen3.8-Flash-Next, MTP spec decode, 2 slots over ONE 200,704-position pool, vision ON, **Strix Halo iGPU** (unified memory) |
| `frank-zealot` | `frank-zealot.service` (root) | `:7771` | llama.cpp (PrismML fork, build 10754) — Ternary-Bonsai-2-27B PQ2_0 GGUF (qwen35 hybrid), 2×200,704 slots, q8_0 K+V, mmproj vision, **RTX 3090** |
## Services Harness-side context windows (`agent/models.yml`): dragoon 155,648,
zealot 200,704 per slot. The models.yml display labels "(dankclaw-gpu)" /
### llama.cpp "(dankclaw-3090)" predate naming cleanup; the hardware column above is
current. Subagent roles `scout`, `sonic`, `designer`, `librarian`,
| Property | Value | `security-reviewer` route to frank-zealot; `reviewer`/`task` run on
|----------|-------| frank-archon (Dankserver).
| **Port** | 7770 |
| **Models** | `frank-default-large` |
## Hardware
| Property | Value |
|----------|-------|
| **CPU** | AMD Ryzen AI MAX+ 395 (16C/16T, Strix Halo) |
| **GPU** | Radeon 8060S integrated (gfx1151, amdgpu) |
| **RAM** | 119 GiB |
| **Storage** | Kingston SNV3S1000G NVMe (931.5 GB), ~676 GB free |
| **OS** | Ubuntu 26.04 LTS, kernel 7.0.0-30-generic |
| **ROCm** | 7.2.4 (driver: 7.0.0-30-generic) |
| **Python** | 3.14.4 (system) |
## Usage
Dankclaw handles complex tasks delegated by subagent overrides. The `frank-default-large` model provides extended context. *Multimodal input support is unverified.*
```bash ```bash
# Health check curl http://192.168.0.143:7770/v1/models # dragoon
curl http://192.168.0.143:7770/health curl http://192.168.0.143:7771/v1/models # zealot
# Test with large model
curl http://192.168.0.143:7770/v1/chat/completions \
-H "Content-Type: application/json" \
-H "Authorization: Bearer <key>" \
-d '{"model":"frank-default-large","messages":[{"role":"user","content":"Hello"}],"max_tokens":32}'
``` ```
## Related Knowledge Bases (sibling project on the workstation) ## Hardware (verified live 2026-10-18)
- **serverAppConfigs** — `/home/dank/Projects/serverAppConfigs/` — Podman deployment config for this host (AI, search, development, observability stack, incl. the Hermes compose service) **plus the LLM inference fleet** (frank-default-large, CIRU ROCmFPX llama.cpp, :7770). The former `vllmScripts` repo merged into it on 2026-08-22 (history preserved). Start at `/home/dank/Projects/serverAppConfigs/docs/index.md` (see `dankclaw/compose.yaml` + `docs/Dankclaw/`; LLM fleet at `docs/LLM/index.md`, deploy runbook at `docs/LLM/deployment.md`). | Property | Value |
|----------|-------|
| **CPU/APU** | AMD Ryzen AI MAX+ 395 (Strix Halo, Radeon 8060S, gfx1151) |
| **dGPU** | NVIDIA GeForce RTX 3090 (moved from Dankserver 2026-09) |
| **RAM** | 121 GiB (mostly usable as GPU unified memory) |
| **Swap** | 64 GiB |
| **OS** | Ubuntu 26.04 LTS, kernel 7.0.0-38-generic |
The pre-rename story (`frank-default-large` on ROCmFPX llama.cpp/CIRU,
262,144-token context) was superseded by the 2026-10-08/09 model-id rename
and the dragoon/zealot engine swaps; the 119→121 GiB RAM figure follows the
live `free` reading.
## Related Knowledge Bases (sibling project)
- **serverAppConfigs** — deployment repo + vault, on this workstation at
`~/Projects/serverAppConfig/` (docs vault: `~/Projects/serverAppConfig/serverAppConfigs-docs/`).
Live runbooks: `LLM/frank-dragoon-flash-server-v2-native.md` and
`LLM/frank-zealot-llama-prism-bonsai2-pq20.md` — deploy-side source of
truth for engines, flags, and restart procedures. Service stack docs under
`Dankclaw/`, `Infrastructure/`.
## See Also ## See Also
- [[models|models]] — Provider definitions - [[dankserver|dankserver]] — the main-model box (frank-archon)
- [[dankserver|dankserver]] — Primary server - [/tools/gitea/index.md](/tools/gitea/index.md) — Gitea stack on this host
- [[network|network]] — Network topology - [[network|network]] — Network topology
omp-docs/system/dankserver.md
+36 -22
View File
@@ -1,22 +1,24 @@
--- ---
type: reference type: reference
title: Dankserver title: Dankserver
description: Primary llama.cpp inference server at 192.168.0.235:7770, serving frank-default-small with 163,840-token context window. description: Radiance inference server at 192.168.0.235:7770, serving frank-archon (Qwen3.8-Flash-Next iq4r, 2x R9700 TP=2, 200,000-token context).
tags: tags:
- network - network
- llamacpp - llamacpp
- inference - inference
- server - server
- unverified
generated: generated:
by: chief-designer/agent by: chief-designer/agent
verified: 2026-08-28 verified: 2026-10-18
status: stable status: stable
--- ---
# Dankserver # Dankserver
Primary llama.cpp inference server for the Frank Program. Serves `frank-default-small` — a fast, capable model with image support. Primary inference server for the Frank Program. Serves `frank-archon`, the
main agent model, from a pair of Radeon AI PRO R9700s (tensor-parallel 2).
The RTX 3090 that used to live here was removed 2026-09-15 and now runs on
Dankclaw.
## Connection Details ## Connection Details
@@ -28,19 +30,24 @@ Primary llama.cpp inference server for the Frank Program. Serves `frank-default-
| **Base URL** | `http://192.168.0.235:7770/v1` | | **Base URL** | `http://192.168.0.235:7770/v1` |
| **API** | OpenAI-compatible completions | | **API** | OpenAI-compatible completions |
| **Authentication** | None | | **Authentication** | None |
| **Systemd unit** | `frank-archon.service` (root) |
## Model ## Model
| Property | Value | | Property | Value |
|----------|-------| |----------|-------|
| **Model ID** | `frank-default-small` | | **Model ID** | `frank-archon` (display name `frank-archon`) |
| **Context Window** | 163,840 tokens | | **Weights** | Qwen3.8-Flash-Next, radiance iq4r (publisher build) |
| **Reasoning** | Supported | | **Engine** | radiance, tensor-parallel 2 across both R9700s |
| **Input Types** | Text, *Image* (unverified) | | **Context Window** | 200,000 tokens (harness `models.yml`; served pool may differ — see runbook) |
`frank-medium` (former dual-GPU mid tier) is masked and retired.
## Usage ## Usage
Dankserver serves the small subagent model `frank-default-small`. Small subagent roles route here unless a role override picks a different model. Dankserver carries the main-session model. Subagent role overrides in
`agent/models.yml` route here for `task` and `reviewer`; scout/sonic/designer
route to Dankclaw.
```bash ```bash
# Health check # Health check
@@ -49,27 +56,34 @@ curl http://192.168.0.235:7770/health
# Quick test # Quick test
curl http://192.168.0.235:7770/v1/chat/completions \ curl http://192.168.0.235:7770/v1/chat/completions \
-H "Content-Type: application/json" \ -H "Content-Type: application/json" \
-d '{"model":"frank-default-small","messages":[{"role":"user","content":"Hello"}],"max_tokens":32}' -d '{"model":"frank-archon","messages":[{"role":"user","content":"Hello"}],"max_tokens":32}'
``` ```
## Hardware ## Hardware (verified live 2026-10-18)
| Property | Value | | Property | Value |
|----------|-------| |----------|-------|
| **CPU** | AMD Ryzen 7 7700X (8C/16T, Raphael) | | **CPU** | AMD Ryzen 7 7700X (8C/16T, Raphael iGPU on board) |
| **GPU** | NVIDIA GeForce RTX 3090 (24 GiB VRAM, EVGA) | | **GPU** | 2× AMD Radeon AI PRO R9700 (Navi 48, 32 GiB each) |
| **RAM** | 60 GiB | | **RAM** | 246 GiB |
| **Swap** | 64 GiB (/swapfile) | | **Swap** | effectively none (~0.1 GiB) — the 64 GiB swapfile is on Dankclaw, not here |
| **Storage** | Kingston SNV3S1000G NVMe (931.5 GB) + md0 RAID (6×18.2T Toshiba, /mnt/entropy, 91T) | | **Storage** | 7× 18.2 TB HDD + 1.8 TB NVMe (layout owned by the deploy repo) |
| **OS** | Ubuntu 26.04 LTS, kernel 7.0.0-30-generic | | **OS** | Ubuntu 26.04.1 LTS, kernel 7.0.0-38-generic |
| **NVIDIA Driver** | 595.84 |
## Related Knowledge Bases (sibling project on the workstation) The old page (verified 2026-08-28) listed an RTX 3090, 60 GiB RAM, and a
64 GiB swapfile here; all three were superseded by the 2026-09 hardware swap.
- **serverAppConfigs** — `/home/dank/Projects/serverAppConfigs/` — Podman deployment config for this host (media and library stack: RomM, Copyparty, Calibre-Web) **plus the LLM inference fleet** (frank-default-small, llama.cpp, :7770). The former `vllmScripts` repo merged into it on 2026-08-22 (history preserved). Start at `/home/dank/Projects/serverAppConfigs/docs/index.md` (see `dankserver/compose.yaml` + `docs/Dankserver/`; LLM fleet at `docs/LLM/index.md`, deploy runbook at `docs/LLM/deployment.md`). ## Related Knowledge Bases (sibling project)
- **serverAppConfigs** — deployment repo + vault, on this workstation at
`~/Projects/serverAppConfig/` (docs vault: `~/Projects/serverAppConfig/serverAppConfigs-docs/`).
Podman/quadlet deploy config for both servers plus the LLM inference fleet.
The live frank-archon runbook (engine flags, KV pool sizing, restart
procedures) is `LLM/frank-archon-radiance-qwen38-iq4r.md` in that vault —
it, not this page, is the deploy-side source of truth.
## See Also ## See Also
- [[models|models]] — Provider definitions - [[dankclaw|dankclaw]] — the other inference box (dragoon + zealot)
- [[dankclaw|dankclaw]] — Secondary server
- [[network|network]] — Network topology - [[network|network]] — Network topology
- [/pi/statusline.md](/pi/statusline.md) — where these models surface in the TUI
omp-docs/system/index.md
+5 -5
View File
@@ -11,8 +11,8 @@ Dankclaw are the inference servers it talks to.
## Network Systems ## Network Systems
- [Dankserver](/system/dankserver.md) — Primary llama.cpp inference server at 192.168.0.235:7770, serving `frank-default-small` (163,840-token context). AMD Ryzen 7 7700X, RTX 3090, Ubuntu 26.04. - [Dankserver](/system/dankserver.md) — Main-model inference server at 192.168.0.235:7770, serving `frank-archon` (radiance Qwen3.8-Flash-Next, 200K ctx). AMD Ryzen 7 7700X, 2× Radeon AI PRO R9700, Ubuntu 26.04.
- [Dankclaw](/system/dankclaw.md) — Secondary inference server at 192.168.0.143:7770, serving `frank-default-large` (262,144-token context). AMD Ryzen AI MAX+ 395 (Strix Halo), Ubuntu 26.04, ROCm. - [Dankclaw](/system/dankclaw.md) — Secondary inference + services box at 192.168.0.143: `frank-dragoon` (:7770, halogen-flash-server on the Strix Halo iGPU) and `frank-zealot` (:7771, llama.cpp on the RTX 3090). AMD Ryzen AI MAX+ 395, Ubuntu 26.04.
## Infrastructure Diagram ## Infrastructure Diagram
@@ -26,8 +26,8 @@ graph TB
end end
subgraph Network[192.168.0.0/24] subgraph Network[192.168.0.0/24]
E[dankserver<br/>192.168.0.235:7770<br/>frank-default-small] E[dankserver<br/>192.168.0.235:7770<br/>frank-archon]
F[dankclaw<br/>192.168.0.143:7770<br/>frank-default-large] F[dankclaw<br/>192.168.0.143:7770 dragoon<br/>:7771 zealot]
end end
D --> E D --> E
@@ -42,7 +42,7 @@ graph TB
The fleet has one sibling OKF knowledge base outside this bundle. Read it for The fleet has one sibling OKF knowledge base outside this bundle. Read it for
deployment and inference details. This bundle links to it from the server pages. deployment and inference details. This bundle links to it from the server pages.
* **serverAppConfigs** — `/home/dank/Projects/serverAppConfigs/` (index: `/home/dank/Projects/serverAppConfigs/docs/index.md`). Podman deployment configuration for both servers: compose files, Caddy reverse proxy, deploy scripts, bats tests, and the Obsidian-vault service docs (Dankclaw, Dankserver, Architecture, Infrastructure) — **plus the LLM inference fleet** (merged from the former `vllmScripts` repo on 2026-08-22, history preserved): llama.cpp on Dankserver (:7770, `frank-default-small`) and CIRU ROCmFPX llama.cpp on Dankclaw (:7770, `frank-default-large`). LLM fleet docs: `docs/LLM/index.md`; deploy runbook: `docs/LLM/deployment.md`. * **serverAppConfigs** — deploy repo + Obsidian vault, on this workstation at `~/Projects/serverAppConfig/` with docs in `~/Projects/serverAppConfig/serverAppConfigs-docs/` (root `index.md` at the vault top — the old `docs/` prefix is gone). Podman deployment configuration for both servers: compose/quadlet files, Caddy reverse proxy, deploy scripts, bats tests, and the vault service docs (Dankclaw, Dankserver, Architecture, Infrastructure) — **plus the LLM inference fleet** (merged from the former `vllmScripts` repo on 2026-08-22, history preserved): radiance frank-archon on Dankserver (:7770), halogen frank-dragoon (:7770) and llama.cpp frank-zealot (:7771) on Dankclaw. The vault's `LLM/` runbooks are the deploy-side source of truth; this bundle documents the agent/harness side.
## Related ## Related
omp-docs/tools/gitea/architecture.md
+4 -5
View File
@@ -5,13 +5,12 @@ description: Gitea container architecture, network topology, and Caddy reverse p
tags: tags:
- gitea - gitea
- architecture - architecture
- unverified verified: 2026-10-18
verified: 2026-08-28
--- ---
# Gitea Architecture # Gitea Architecture
Three quadlet-managed containers on a shared private Podman network (rootless, user `dank`). Gitea connects to PostgreSQL via network DNS. Caddy proxies HTTP/S to Gitea. Two quadlet-managed containers (Gitea, PostgreSQL) on a shared private Podman network (rootless, user `dank`). Gitea connects to PostgreSQL via network DNS. The fleet Caddy (separate stack, see [/caddy/index.md](/caddy/index.md)) proxies HTTP/S to Gitea — the old dedicated `gitea-caddy` container is retired.
## Network Topology ## Network Topology
@@ -63,10 +62,10 @@ Key environment variables:
- `DATABASE_HOST=gitea-postgres` (network DNS) - `DATABASE_HOST=gitea-postgres` (network DNS)
- `DATABASE_NAME=gitea` - `DATABASE_NAME=gitea`
- `DATABASE_USER=gitea` - `DATABASE_USER=gitea`
- `DATABASE_PASSWD` from `/opt/gitea/.env` (mode 0600) - `DATABASE_PASSWD` from `/home/dank/Containers/gitea/env` (mode 0600)
- `USER_UID=1000`, `USER_GID=1000` - `USER_UID=1000`, `USER_GID=1000`
Gitea writes `/data/gitea/conf/app.ini` on first start (host: `/opt/gitea/data/gitea-gitea/gitea/conf/app.ini`). The `[database] HOST` and `PASSWD` lines in app.ini override the env vars. When you rename the database container, edit the `HOST` line in app.ini as well. Gitea writes `/data/gitea/conf/app.ini` on first start (host: `/home/dank/Containers/gitea/data/gitea/conf/app.ini`). The `[database] HOST` and `PASSWD` lines in app.ini override the env vars. When you rename the database container, edit the `HOST` line in app.ini as well.
## Ports ## Ports
omp-docs/tools/gitea/data-persistence.md
+9 -10
View File
@@ -1,24 +1,23 @@
--- ---
type: reference type: reference
title: Gitea Data Persistence title: Gitea Data Persistence
description: Gitea data persistence, volume mounts, ownership, and backup strategy on dankclaw. description: Gitea data persistence, volume mounts, ownership, and backup strategy on dankclaw (Containers/gitea layout).
tags: tags:
- gitea - gitea
- data - data
- unverified verified: 2026-10-18
verified: 2026-08-28
--- ---
# Gitea Data Persistence # Gitea Data Persistence
All data lives on host bind mounts under `/opt/gitea/data/`. Containers are ephemeral. Quadlet stops remove the container (`podman run --rm --replace`). The next start recreates it. Data survives. All data lives on host bind mounts under `/home/dank/Containers/gitea/` (fleet storage standard since 2026-09-01; quadlet units re-pointed from the old `/opt/gitea/data/` tree, which lingers on disk as a leftover — never write to it). Containers are ephemeral. Quadlet stops remove the container (`podman run --rm --replace`). The next start recreates it. Data survives.
## Volume Layout ## Volume Layout
| Host Path | Container Mount | Contents | | Host Path | Container Mount | Contents |
|---|---|---| |---|---|---|
| `/opt/gitea/data/gitea-gitea/` | `/data` | Git repositories, avatars, attachments, LFS objects, `app.ini` | | `/home/dank/Containers/gitea/data/` | `/data` (gitea-server) | Git repositories, avatars, attachments, LFS objects, `app.ini` |
| `/opt/gitea/data/gitea-postgres/` | `/var/lib/postgresql/data` | PostgreSQL WAL, tables, indexes | | `/home/dank/Containers/gitea/postgres/` | `/var/lib/postgresql/data` (gitea-postgres) | PostgreSQL WAL, tables, indexes |
## Ownership ## Ownership
@@ -37,7 +36,7 @@ podman exec --user 1000 gitea-server sed -i 's/old/new/' /data/gitea/conf/app.in
Tar the entire data directory. This captures Gitea repos and PostgreSQL data in one archive. Tar the entire data directory. This captures Gitea repos and PostgreSQL data in one archive.
``` ```
tar czf gitea-backup-$(date +%F).tar.gz -C /opt/gitea data/ tar czf gitea-backup-$(date +%F).tar.gz -C /home/dank/Containers/gitea data/ postgres/
``` ```
### PostgreSQL-only backup ### PostgreSQL-only backup
@@ -48,17 +47,17 @@ Use `pg_dump` for a portable SQL dump. Useful for restoring to a different Postg
podman exec -e PGPASSWORD="$GITEA_DB_PASSWORD" gitea-postgres pg_dump -U gitea gitea > gitea-db-$(date +%F).sql podman exec -e PGPASSWORD="$GITEA_DB_PASSWORD" gitea-postgres pg_dump -U gitea gitea > gitea-db-$(date +%F).sql
``` ```
Set `PGPASSWORD` from `/opt/gitea/.env` (mode 0600). Set `PGPASSWORD` from `/home/dank/Containers/gitea/env` (mode 0600, `GITEA_DB_PASSWORD`).
### Restore procedure ### Restore procedure
1. Stop the stack: `systemctl --user stop gitea-server gitea-postgres` 1. Stop the stack: `systemctl --user stop gitea-server gitea-postgres`
2. Restore data: `tar xzf backup.tar.gz -C /opt/gitea/` 2. Restore data: `tar xzf backup.tar.gz -C /home/dank/Containers/gitea/`
3. Start the stack: `systemctl --user start gitea-postgres gitea-server` 3. Start the stack: `systemctl --user start gitea-postgres gitea-server`
## Data Growth ## Data Growth
- Git repositories grow with each commit and push. Monitor with `du -sh /opt/gitea/data/gitea-gitea/git/repositories/`. - Git repositories grow with each commit and push. Monitor with `du -sh /home/dank/Containers/gitea/data/git/repositories/`.
- PostgreSQL WAL files accumulate. VACUUM via `podman exec gitea-postgres psql -U gitea -c "VACUUM;"`. - PostgreSQL WAL files accumulate. VACUUM via `podman exec gitea-postgres psql -U gitea -c "VACUUM;"`.
- Gitea's log files grow with usage. - Gitea's log files grow with usage.
omp-docs/tools/gitea/index.md
+16 -16
View File
@@ -1,11 +1,11 @@
# Gitea on dankclaw # Gitea on dankclaw
Private Git hosting on dankclaw. Three quadlet-managed containers in the rootless podman session of user `dank`: Gitea, PostgreSQL, Caddy. Private Git hosting on dankclaw. Two quadlet-managed containers in the rootless podman session of user `dank`: Gitea and PostgreSQL, sharing a dedicated network unit. The former `gitea-caddy` container is **retired** — the canonical fleet Caddy (`caddy.service`, see [/caddy/index.md](/caddy/index.md)) fronts `gitea.franksdank.cloud`; do not recreate the retired unit.
**Host:** dankclaw (71.227.227.172) **Host:** dankclaw (192.168.0.143 LAN)
**Config:** `~/.config/containers/systemd/gitea-{postgres,server,caddy}.container` + `gitea.network` **Config:** `~/.config/containers/systemd/gitea-{postgres,server}.container` + `gitea.network`
**Local access:** `http://dankclaw:3000` **Local access:** `http://dankclaw:3000` (verified 2026-10-18)
**Domain:** `https://gitea.franksdank.cloud` (DNS pending) **Domain:** `https://gitea.franksdank.cloud` (live; served by fleet Caddy, DNS-01 TLS)
## Architecture ## Architecture
@@ -13,7 +13,7 @@ Private Git hosting on dankclaw. Three quadlet-managed containers in the rootles
|---|---|---|---| |---|---|---|---|
| `gitea-server` | `gitea-server.service` | 3000 (HTTP), 2222 (SSH) | Git web UI, API, SSH daemon | | `gitea-server` | `gitea-server.service` | 3000 (HTTP), 2222 (SSH) | Git web UI, API, SSH daemon |
| `gitea-postgres` | `gitea-postgres.service` | 5432 (internal) | Database | | `gitea-postgres` | `gitea-postgres.service` | 5432 (internal) | Database |
| `gitea-caddy` | `gitea-caddy.service` | 80, 443 | Reverse proxy, auto-TLS | | (network) | `gitea-network.service` | — | quadlet `gitea.network` bring-up |
The containers share the private network `systemd-gitea` (quadlet `gitea.network`, DNS enabled). The automatic `podman` default network has DNS disabled; do not run the stack on it. The containers share the private network `systemd-gitea` (quadlet `gitea.network`, DNS enabled). The automatic `podman` default network has DNS disabled; do not run the stack on it.
@@ -23,21 +23,21 @@ All commands run as `dank` on dankclaw.
| Action | Command | | Action | Command |
|---|---| |---|---|
| Start all | `systemctl --user start gitea-postgres gitea-server gitea-caddy` | | Start all | `systemctl --user start gitea-postgres gitea-server` |
| Stop all | `systemctl --user stop gitea-caddy gitea-server gitea-postgres` | | Stop all | `systemctl --user stop gitea-server gitea-postgres` |
| Restart Gitea only | `systemctl --user restart gitea-server` | | Restart Gitea only | `systemctl --user restart gitea-server` |
| Follow logs | `podman logs -f gitea-server` or `journalctl --user -u gitea-server -f` | | Follow logs | `podman logs -f gitea-server` or `journalctl --user -u gitea-server -f` |
| Check status | `systemctl --user status gitea-postgres gitea-server gitea-caddy` | | Check status | `systemctl --user status gitea-postgres gitea-server` |
## Data Persistence ## Data Persistence
All data lives on host bind mounts under `/opt/gitea/data/`. Containers are ephemeral. Stopping a quadlet unit removes its container; the next start recreates it. Volumes survive. All data lives on host bind mounts under `/home/dank/Containers/gitea/` (fleet storage standard since 2026-09-01; verified live 2026-10-18). Containers are ephemeral. Stopping a quadlet unit removes its container; the next start recreates it. Volumes survive. The old `/opt/gitea/` tree remains on disk as a leftover — do not use it.
| Volume Path | Container Mount | Contents | | Path | Contents |
|---|---|---| |---|---|
| `/opt/gitea/data/gitea-gitea/` | `/data` | Git repositories, app.ini, attachments | | `/home/dank/Containers/gitea/data/` | Git repositories, app.ini, attachments |
| `/opt/gitea/data/gitea-postgres/` | `/var/lib/postgresql/data` | PostgreSQL data files | | `/home/dank/Containers/gitea/postgres/` | PostgreSQL data files |
| `/opt/gitea/data/caddy/data/` | `/root/.local/share/caddy` | Caddy configuration, TLS certs | | `/home/dank/Containers/gitea/env` | EnvironmentFile (mode 0600; `GITEA_DB_PASSWORD`) |
See [[data-persistence|data-persistence]] for backup and restore. See [[data-persistence|data-persistence]] for backup and restore.
@@ -49,7 +49,7 @@ See [[management|management]] for boot persistence details and troubleshooting.
## Repo Copies ## Repo Copies
The quadlet files, Caddyfile, and `.env.example` are tracked in the `serverAppConfigs` repo under `dankclaw/gitea/`. The live password lives only in `/opt/gitea/.env` on the host (mode 0600). The quadlet files and `.env` templates are tracked in the `serverAppConfigs` deploy repo; the sibling vault page `Infrastructure/Gitea.md` (in `~/Projects/serverAppConfig/serverAppConfigs-docs/`) is the deploy-side source of truth. Secrets live only on the host under `Containers/gitea/` (mode 0600), never in either docs tree.
## See Also ## See Also
omp-docs/tools/gitea/management.md
+4 -5
View File
@@ -6,8 +6,7 @@ tags:
- gitea - gitea
- management - management
- quadlet - quadlet
- unverified verified: 2026-10-18
verified: 2026-08-28
--- ---
# Gitea Management # Gitea Management
@@ -45,8 +44,8 @@ After editing a quadlet file: run `systemctl --user daemon-reload`, then restart
| File | Path | | File | Path |
|---|---| |---|---|
| Quadlet units | `~/.config/containers/systemd/gitea-*.container`, `gitea.network` | | Quadlet units | `~/.config/containers/systemd/gitea-*.container`, `gitea.network` |
| Secrets | `/opt/gitea/.env` (mode 0600, `GITEA_DB_PASSWORD`) | | Secrets | `/home/dank/Containers/gitea/env` (mode 0600, `GITEA_DB_PASSWORD`) — quadlet `EnvironmentFile` |
| Gitea app config | `/opt/gitea/data/gitea-gitea/gitea/conf/app.ini` (container-owned, UID 100999) | | Gitea app config | `/home/dank/Containers/gitea/data/gitea/conf/app.ini` (container-owned, UID 100999) |
Repo copies: `serverAppConfigs/dankclaw/gitea/` (quadlet files, `.env.example`). Copy edits to the target, then `daemon-reload` + restart. Repo copies: `serverAppConfigs/dankclaw/gitea/` (quadlet files, `.env.example`). Copy edits to the target, then `daemon-reload` + restart.
@@ -62,7 +61,7 @@ Gitea handles database migrations automatically on startup. PostgreSQL version b
### Gitea cannot reach the database ### Gitea cannot reach the database
Check the `[database] HOST` line in `/opt/gitea/data/gitea-gitea/gitea/conf/app.ini`. It must be `gitea-postgres:5432`. app.ini overrides the `DATABASE_HOST` env var. Check the `[database] HOST` line in `/home/dank/Containers/gitea/data/gitea/conf/app.ini`. It must be `gitea-postgres:5432`. app.ini overrides the `DATABASE_HOST` env var.
Then check name resolution from the container: Then check name resolution from the container:
omp-docs/tools/llama-cpp/index.md
+1 -1
View File
@@ -50,7 +50,7 @@ llama-server -hf ggml-org/gemma-3-1b-it-GGUF
**Defaults**: Listens on `127.0.0.1:8080`. Single slot (one concurrent request). **Defaults**: Listens on `127.0.0.1:8080`. Single slot (one concurrent request).
> **System note:** On this network the Pi inference hosts do not use the default port. Pi serves `frank-default-small` (dankserver) and `frank-default-large` (dankclaw), each on port `7770`. The local Ornith host runs on port `8080`. See [Pi Models Configuration](../../pi/models.md). > **System note:** On this network the fleet inference hosts do not use the default port. As of 2026-10 the only llama.cpp endpoint is `frank-zealot` on dankclaw **:7771** (PrismML fork build); `frank-dragoon` (dankclaw :7770, halogen-flash-server) and `frank-archon` (dankserver :7770, radiance) are different engines — see [System hosts](/system/index.md). The pi-era `frank-default-small`/`frank-default-large` llama.cpp pair (each :7770) is retired; [Pi Models Configuration](../../pi/models.md) is a pi-era archive.
--- ---