vh
39da1d4a97
The board mixed tools with endpoints. A vLLM seat whose href is a /docs page
sat in the same band as ComfyUI; the MQTT broker and the RustDesk relay, which
have no page at all, sat in Apps; and `Service Networking` was thirteen members
spanning three AdGuards, five Dockges, two Traefiks and four headless agents.
Every group is now one of two kinds and they never mix. TOOLS are expanded and
sit at the top of their tab. ENDPOINTS — an API, a broker, a background agent,
an href that is /docs or /ping or nothing — carry `initiallyCollapsed: true`
and sit at the bottom. Collapsed is not hidden: the eyebrow and its rule still
render, so the tab still says the thing exists and one click expands it.
A second rule fell out of the same pass and now shapes the group boundaries: a
group's members should all carry a widget or none should. A stat strip makes a
card ~50px taller, so one widget card in a row of plain ones opens a void under
the plain ones. That is why AdGuard and Traefik get their own groups rather
than sharing one with Dockge, and it is most of why the old Service Networking
band looked broken. AdGuard (ANA) was the last short card in its row and now
carries the same query/blocked/latency strip as its two siblings — one
infra-ops AdGuard login authenticates against all three instances, verified
against each; it lives in that stack's .env on the host and is vaulted.
The sixteen GPU-backed model seats were deliberately NOT relabelled.
`homepage.group` is read at container creation, so clearer names for
`AI - Inference` and friends would have cost a recreate on six vLLM seats, four
eval seats and four TTS engines — multi-minute model reloads on endpoints peers
reach through the gateway. Order plus `initiallyCollapsed` buys the same
separation for nothing, so those names stay as they are on purpose.
28 containers that ARE cheap to bounce were relabelled, across five hosts, via
rerunnable elway playbooks. Their label steps are gated on the old value still
being present, so a second run reports skipped rather than churning. Two verify
steps were wrong on first contact and are fixed with the reason recorded: the
traefik check raced its own recreate, and asserting a model seat is "running"
cannot answer "did I bounce it" when a seat may be legitimately stopped —
container age can, and now does.
The canonical stacks/ tree was synced to the deployed labels afterwards, so
intent and reality agree again on all fourteen tracked stacks.
Also documents the real nature of the post-recreate blank dashboard, which cost
~25 minutes here and an hour on 2026-08-19. `initialSettings":{}` in the served
HTML is the catch branch of the page's data loader, not a warm-up and not a
cache — and the error can vanish entirely, because the logger is assigned inside
the same try and the catch only logs if the logger exists. Ruled out by
measurement this time: all four API routes return 200 with correct content while
the page serves {}, and the previous known-good settings.yaml reproduces it
identically. The README now carries the one-command test and the next lead.
Before/after, all four tabs: http://10.100.10.50:8090/b/homepage-relayout/
99 lines
4.5 KiB
YAML
99 lines
4.5 KiB
YAML
services:
|
|
searxng:
|
|
image: searxng/searxng:latest
|
|
container_name: searxng
|
|
restart: unless-stopped
|
|
# ------------------------------------------------------------------
|
|
# Port binding — 9996 on all interfaces.
|
|
# Change to "127.0.0.1:9996:8080" to restrict to localhost only.
|
|
# Traefik handles public routing and TLS via the labels below.
|
|
# ------------------------------------------------------------------
|
|
ports:
|
|
- 9996:8080
|
|
# ------------------------------------------------------------------
|
|
# Volumes
|
|
# Config: settings.yml bind-mounted read-only into the container.
|
|
volumes:
|
|
- /opt/docker/conf/searxng/searxng-settings.yml:/etc/searxng/settings.yml:ro
|
|
# ------------------------------------------------------------------
|
|
# Environment — see https://docs.searxng.org/admin/settings/index.html
|
|
# SEARXNG_SECRET — required for cryptographic signing (cookies, etc.)
|
|
# BASE_URL — public URL SearXNG reports in pages/RSS/OPDS
|
|
# INSTANCE_NAME — shown in the page title / footer
|
|
# ------------------------------------------------------------------
|
|
environment:
|
|
- SEARXNG_SECRET=${SEARXNG_SECRET}
|
|
# searxng.ana.internal, not the old searxng.pfi.local (migrated
|
|
# 2026-08-19). `.local` is reserved for mDNS, so the old name was a
|
|
# standards collision that happened to work; `.internal` is ICANN-
|
|
# reserved for exactly this. The name is served by the fleet's AdGuard
|
|
# resolvers from dns/internal.yaml — see scripts/dns-sync.py.
|
|
- BASE_URL=https://searxng.ana.internal/
|
|
- INSTANCE_NAME=SearXNG
|
|
# ------------------------------------------------------------------
|
|
# Resource limits — tune for VM 102's available RAM/CPU
|
|
# ------------------------------------------------------------------
|
|
deploy:
|
|
resources:
|
|
limits:
|
|
memory: 512M
|
|
cpus: "1.0"
|
|
reservations:
|
|
memory: 128M
|
|
# ------------------------------------------------------------------
|
|
# Health check — SearXNG /healthz is the canonical liveness probe.
|
|
#
|
|
# ⚠️ `--tries=1` MUST keep its `=1`. This read `- --tries` / `- --spider`
|
|
# as two separate argv entries until 2026-08-18, and in that form wget
|
|
# consumed `--spider` as the VALUE of `--tries` — so spider mode never
|
|
# engaged and every probe DOWNLOADED the response to a file instead of
|
|
# just checking it. By the time it was caught the container's working
|
|
# directory held 295,287 `healthz.N` files, one per probe since April,
|
|
# and wget had to scan all of them to pick the next free filename. That
|
|
# scan is what intermittently blew the 10s timeout and made the card on
|
|
# the dashboard flap UNHEALTHY while the service itself was fine. It was
|
|
# self-worsening: every probe made the next one slower.
|
|
#
|
|
# The junk lived in the container's writable layer (the only volume here
|
|
# is the read-only settings mount), so recreating the container cleared
|
|
# it. Symptom to watch for if this regresses: `docker exec searxng ls |
|
|
# wc -l` climbing, and health log entries reading
|
|
# "Health check exceeded timeout (10s)".
|
|
# ------------------------------------------------------------------
|
|
healthcheck:
|
|
test:
|
|
- CMD
|
|
- wget
|
|
- --no-verbose
|
|
- --tries=1
|
|
- --spider
|
|
- http://localhost:8080/healthz
|
|
interval: 30s
|
|
timeout: 10s
|
|
retries: 3
|
|
start_period: 15s
|
|
networks:
|
|
- tnet
|
|
labels:
|
|
# Traefik configuration — auto-discovery via Docker provider
|
|
- traefik.enable=true
|
|
# Both names during the migration: `.internal` is the real one now, and
|
|
# the old `.pfi.local` is kept as a fallback so anything still pointing
|
|
# at it (a bookmark, a hardcoded config elsewhere) does not break the
|
|
# day the name changes. Drop the second Host() once nothing uses it —
|
|
# the Traefik access log will tell you when that is.
|
|
- traefik.http.routers.searxng.rule=Host(`searxng.ana.internal`) || Host(`searxng.pfi.local`)
|
|
- traefik.http.routers.searxng.entrypoints=websecure
|
|
- traefik.http.routers.searxng.tls=true
|
|
- traefik.http.routers.searxng.service=searxng
|
|
- traefik.http.services.searxng.loadbalancer.server.port=8080
|
|
- homepage.group=Daily
|
|
- homepage.name=SearXNG
|
|
- homepage.icon=si-searxng
|
|
- homepage.description=Privacy-respecting meta-search
|
|
- homepage.href=http://10.250.50.70:9996
|
|
networks:
|
|
tnet:
|
|
name: traefik-net
|
|
external: true
|