Hendrik 570a524d86
All checks were successful
Build & Publish Docker Image / build-and-push (push) Successful in 53s
fix(search): unblock SearXNG 403 — config + headers
SearXNG returned 403 for every query, logging
'X-Forwarded-For nor X-Real-IP header is set!'. Two fixes, both needed:

1. searxng/settings.yml was being overwritten by SearXNG's default
   config in fresh volumes. Explicitly set limiter: false,
   public_instance: false, and move secret_key to env lookup via
   ${SEARXNG_SECRET:-…}. Force a well-known JSON format list.

2. Even with the limiter off, SearXNG's bot detection still nags on
   missing forwarder headers. The Node client now sends
   X-Forwarded-For: 127.0.0.1, X-Real-IP: 127.0.0.1 and Accept: json
   deterministically. Done via a new extraHeaders option on the http
   wrapper.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-17 16:56:13 +02:00
2026-04-17 14:56:20 +02:00
Description
Kochwas — selbstgehostete Rezept-PWA für die Familie
2.9 MiB
Languages
TypeScript 66.7%
Svelte 32.6%
Dockerfile 0.4%
JavaScript 0.2%
HTML 0.1%