At present, a single user-defined health check runs after a new container is started, but before it receives connections. Essentially, the Dokku host curls the new container, requesting the root URL (see #2148 and #2156).
A 200 response from the root URL isn't necessarily a good indicator that the new container is healthy. The root URL is also slow to respond (see #1857). job-server has a HealthCheck view, which returns a 200 response (jobserver/views/health_check.py, https://jobs.opensafely.org/health-check/). OpenCodelists should have the same; it should be used by Freshping.
At present, a single user-defined health check runs after a new container is started, but before it receives connections. Essentially, the Dokku host
curlsthe new container, requesting the root URL (see #2148 and #2156).https://github.com/opensafely-core/opencodelists/blob/b3da21a5125a19b968d99f17da7fe3d0da8667e3/app.json#L9-L26
A 200 response from the root URL isn't necessarily a good indicator that the new container is healthy. The root URL is also slow to respond (see #1857). job-server has a
HealthCheckview, which returns a 200 response (jobserver/views/health_check.py, https://jobs.opensafely.org/health-check/). OpenCodelists should have the same; it should be used by Freshping.