fix: use readiness endpoint for container healthchecks #3
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/mobile-title-healthcheck"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
/api/readyas a lightweight process readiness endpointHEALTHCHECKat/api/readyso the container can become healthy even if the mounted wiki still needs path/permission debugging/api/healthas the deep wiki mount/page-count diagnostic and document the splitRoot cause
The current Docker healthcheck calls
/api/health, which deep-loads the mounted wiki. I reproduced that a missing/unreadable/data/wikimakes/api/healthreturn503while the server itself is up and logging normally. Changingread_onlydoes not affect that failure mode.Testing
healthyvia/api/readywhile/api/healthreturns 503 diagnostic; mounted wiki is healthy and/api/healthreturns 200