1a44c1403f
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
18 lines
1.2 KiB
Markdown
18 lines
1.2 KiB
Markdown
# Changelog
|
|
|
|
## 2026-06-22 — gitea healthcheck fix (unattended test campaign)
|
|
- **gitea**: healthcheck probe repointed `/api/v1/version` → `/api/healthz` (docker HC + controller
|
|
`.felhom.yml` probe), `start_period` 30s → 90s.
|
|
- Surfaced during the Phase-2 deploy sweep: a fresh gitea reported `unhealthy` because
|
|
`/api/v1/version` returns 404 until the install wizard / INSTALL_LOCK completes, while the
|
|
container was serving fine on :3000 (`/api/healthz` → 200). Same class as the komga fix.
|
|
|
|
## 2026-06-22 — komga healthcheck fix (unattended test campaign)
|
|
- **komga**: healthcheck probe repointed `/api/v1/actuator/health` → `/actuator/health`.
|
|
- Root cause: komga's Spring Boot actuator endpoint is served unauthenticated at `/actuator/health`
|
|
(HTTP 200), while everything under the `/api/v1` prefix is auth-gated — so the old probe got
|
|
HTTP 401, `curl -f` exited 22, and the container reported `unhealthy` despite serving normally
|
|
on :25600. Diagnosed live on guest 9201 (probe matrix: `/`, `/actuator/health`,
|
|
`/api/v1/oauth2/providers`, `/login` all 200; `/api/v1/actuator/health` → 401).
|
|
- The `gotson/komga:1.20.0` image ships `curl` (verified), so the probe tool is unchanged.
|