Files

T

Frank e3eb5334cb feat: initialize serverAppConfigs with podman stacks for Dankserver and Dankclaw

- Dankserver stack: RomM, Copyparty, Calibre-Web, node-exporter
- Dankclaw stack: Gluetun VPN (SearXNG tunnel), SearXNG+Valkey, ComfyUI
  (CPU backend), OpenWebUI, Hermes, Gitea+Postgres (migrated), Caddy
  reverse proxy, Grafana+Prometheus+Loki+Alloy observability
- Caddyfiles with .local hostname convention and basicauth homepage
- bind-mount storage policy, no named volumes
- deploy.sh mirroring vllmScripts git workflow (push -> pull -> restart -> health)
- docs/ Obsidian vault: per-service docs from frank-default-small research
  subagents (promtail EOL -> Alloy; gitea SECRET_KEY preservation; ComfyUI --cpu)
- bats test suite at 6 seams — 22 tests green

2026-08-13 20:19:41 -07:00

1.2 KiB

Raw Blame History

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

services:
  valkey:
    image: valkey/valkey:9-alpine
    restart: always
    volumes:
      - /opt/searxng/valkey:/data

SearXNG connects to it via settings.yml:

valkey:
  url: "valkey://searxng-valkey:6379/0"

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.

1.2 KiB Raw Blame History