cmd/golangorg: migrate from legacy to split health checks

For now, continue to use the existing /_ah/health HTTP endpoint
for both the liveness and readiness checks. This is simple and
close to the previous legacy health check behavior. In the future,
we can consider making the readiness check more sophisticated.

This change should make golangorg deployable again after the
deprecation of legacy health checks.¹

¹ https://cloud.google.com/appengine/docs/flexible/go/migrating-to-split-health-checks

Change-Id: Ia68d3b260dd3a5b66f969318a04b8f97639701d6
Reviewed-on: https://go-review.googlesource.com/c/website/+/201743
Reviewed-by: Katie Hockman <katie@golang.org>
1 file changed
tree: 120e67e5e84d860899a25953e1cd6125c51bd750
  1. AUTHORS
  2. CONTRIBUTING.md
  3. CONTRIBUTORS
  4. LICENSE
  5. PATENTS
  6. README.md
  7. cmd/
  8. codereview.cfg
  9. content/
  10. favicon.ico
  11. go.mod
  12. go.sum
  13. internal/
  14. robots.txt
README.md

Go Website

This repository holds the Go Website server code and content.

Download/Install

The easiest way to install is to run go get -u golang.org/x/website. You can also manually git clone the repository to $GOPATH/src/golang.org/x/website.

Report Issues / Send Patches

This repository uses Gerrit for code changes. To learn how to submit changes to this repository, see https://golang.org/doc/contribute.html.

The main issue tracker for the website repository is located at https://github.com/golang/go/issues. Prefix your issue with “x/website:” in the subject line, so it is easy to find.