Frank
93d1181fee
- Migrate all 127 non-reserved docs to OKF v0.1 frontmatter (type/description/tags/timestamp); fix 13 YAML issues, 2 duplicate-FM blocks, strip reserved-page FM - Restructure log.md to OKF (## YYYY-MM-DD, newest-first) - Fact-check against scripts/AGENTS.md ground truth: fix 6 false 'Active' banners on retired runbooks, 96->114 GiB GTT, deployment.md vs deploy-plan.py/deploy-remote.sh, Deployment Flow frank-medium=Quadlet, Calibre 9.9.0->9.15.0 + CVE-2025-7404 conflation, Copyparty v1.20.24, RomM 5.3.0 breaking change - Move *arr docs to new FrankBook-Pro/ section (git mv, link-safe) - Write active runbook bodies from ground truth (frank-large, frank-small) - Add 3 research briefs + HTML report: Local TTS and Voice Cloning, AI Job Search and Resume Tools, Most Popular Self-Hosted AI Apps (Jun-Sep 2026) - Add upstream-version rows to ComfyUI/OpenWebUI/Hermes app docs - All 336 tests pass; 136 pages, 0 unresolved wikilinks
1.6 KiB
1.6 KiB
type, description, tags, timestamp
| type | description | tags | timestamp | ||
|---|---|---|---|---|---|
| reference | Valkey is the cache and limiter store for SearXNG. |
|
2026-08-28 |
Valkey
Valkey is the cache and limiter store for SearXNG. It replaces Redis as the default in the official SearXNG deployment.
Host: Dankclaw — Docs: https://valkey.io
Facts (from research)
| Item | Value |
|---|---|
| Image | valkey/valkey:9-alpine |
| Port | 6379 (internal, on the SearXNG network) |
| Role | SearXNG limiter + result cache |
Why Valkey
The official SearXNG docker-compose ships a searxng-valkey container. Valkey is the Redis fork under the Linux Foundation umbrella; the SearXNG project moved to it as the default cache.
Configuration
The valkey unit is searxng-valkey.container (see SearXNG for the trio). It joins the searxng network and is reachable by the name searxng-valkey (container name) and the alias valkey:
[Container]
ContainerName=searxng-valkey
Network=searxng.network
NetworkAlias=valkey
Image=docker.io/valkey/valkey:9-alpine
Volume=/opt/searxng/valkey:/data
SearXNG connects to it via settings.yml:
valkey:
url: "valkey://searxng-valkey:6379/0"
It sets WantedBy=default.target. User linger is on, so it starts at boot.
Volumes
| Container path | Host path (convention) |
|---|---|
/data |
/opt/searxng/valkey |
Gotchas
- The limiter relies on Valkey; without it SearXNG falls back to in-memory state and rate limiting is per-restart.
- Keep Valkey on the same podman network as SearXNG.
See Also
- SearXNG — the consumer
- Dankclaw Stack