fix(filebrowser_quantum): simplify the healthcheck

Curl the app root: v2 answers 200, or 301 to the baseURL, which curl -f
accepts, so the baseURL no longer has to be read from the config.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

filebrowser_quantum/CHANGELOG.md

@@ -10,7 +10,7 @@
   - Everything else is kept, including extra sources and auth/OIDC settings.
   - Users, shares and settings in `/config/database.db` are migrated to `/config/database.sqlite` on first start.
 - `http.trustProxyHeaders` is set to `true`, because the add-on always runs behind nginx on a subpath.
-- The container healthcheck now uses upstream's `/health` endpoint.
+- The container healthcheck now checks FileBrowser directly on port 8080 instead of an nginx stub.
 - Direct access on port 8071 no longer passes on a client-supplied `X-Forwarded-For`, so the IP-based login lockout cannot be bypassed now that proxy headers are trusted. Ingress keeps the forwarded chain.
 
 ## 2.0.0 (2026-10-10)

filebrowser_quantum/Dockerfile

@@ -116,4 +116,4 @@ LABEL \
 #################
 
 HEALTHCHECK --interval=30s --timeout=3s --start-period=10s --retries=3 \
-  CMD b="$(yq '.http.baseURL' /config/config.yaml)" && curl -f "http://localhost:8080${b%/}/health" || exit 1
+  CMD curl -fs -o /dev/null http://localhost:8080/ || exit 1