deploy: ship the search block, so the live web is on for this box

Owner's call. The code default stays off — no `search` block still means no
query leaves the LAN — but the deployed config now carries one, so a question
that is not about him reaches SearXNG before it reaches the ZIMs.

Nothing runs at http://searxng:8080 on homesrv yet. That is the designed
degradation and not a broken turn: an unreachable instance falls through to
Kiwix and she never says the search failed.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
kami
2026-08-02 02:30:01 +04:00
parent 612ca8cf1b
commit 2150a18e98
3 changed files with 25 additions and 4 deletions
+4 -3
View File
@@ -73,10 +73,11 @@ What it does and does not do:
- feed notes are **not** part of recall. "что я говорил про X" searches what he
said; headlines are read back only by asking about the feeds.
### Searching the web (`search`, also off by default)
### Searching the web (`search`, on in this deploy)
There is no `search` block either, so no query leaves the LAN. Switching it on
points her at a self-hosted SearXNG:
`deploy/mavend.json` ships a `search` block, so a question that is not about him
reaches a self-hosted SearXNG before it reaches the ZIMs. Delete the block and
no query leaves the LAN again. The shipped shape:
```json
"search": {