dank/serverAppConfigs
1
0
Fork 0
Code Issues 6 Pull Requests Actions Packages Projects Releases Wiki Activity

SearXNG docs: document quadlet boot-persistence for the trio

Browse Source 
Update SearXNG, Gluetun, and Valkey to describe the quadlet units instead of
compose: searxng sets Network=gluetun.container, the units install to
~/.config/containers/systemd/, and scripts/deploy-searxng-quadlet.sh deploys
them. Add a Boot Persistence section to the Stack doc. Correct the Gluetun
tunnel check (the :8000 server 404s; verify tun0 instead) and note the pinned
10.89.2.0/24 subnet.
This commit is contained in:
Frank
2026-08-18 23:42:45 -07:00
parent 71fe8c008f
commit f488382b08
4 changed files with 51 additions and 24 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/Dankclaw/Dankclaw Stack.md
+6
View File
@@ -40,6 +40,12 @@ The last two rows are bare-metal systemd services, not containers. The
2026-08-17 redo, `frank-default-large` runs llama.cpp FastMTP on
Dankserver; `frank-default-small` runs vLLM on Dankclaw.
## Boot Persistence
The Gitea trio and the SearXNG trio (gluetun, searxng, valkey) run as quadlet units, so they start at boot. User linger is on. ComfyUI runs as a systemd unit around a bare process. The remaining services in the table are defined in `compose.yaml` and are not yet boot-persistent.
Deploy the SearXNG trio with `scripts/deploy-searxng-quadlet.sh dankclaw`. The Gitea units install to `~/.config/containers/systemd/` (see [[Gitea]]).
## Routing Rules
- SearXNG outbound traffic exits through the [[Gluetun]] VPN container.