You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 19, 2023. It is now read-only.
I'm working with Docker containers and my gaeapp has 2 supervisor services running:
nginx
php-fpm
I need to configure my /rediness_check and /liveness_check to make sure those services are running. I tried to implement the custom path on my default.yaml file:
Custom healthchecks are largely going to be up to the person implementing to make it happen. The docs advise you to specify a custom URL but the URL you specified is going to be matched by the regular expression in this file and not passed on to your application.
Instead you should point the rediness and liveness checks at your own URL like ${DOCUMENT_ROOT}/_app/health.php.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm working with Docker containers and my gaeapp has 2 supervisor services running:
I need to configure my
/rediness_check
and/liveness_check
to make sure those services are running. I tried to implement the custom path on my default.yaml file:and it didn't worked the liveness_check started returning a 301 instead and there was no request to my path. It would be nice to have better documentation on this or some samples using custom health checks that are supposedly supported by the docs: https://cloud.google.com/appengine/docs/flexible/php/reference/app-yaml#liveness_checks
The text was updated successfully, but these errors were encountered: