|author||Dmitri Shuralyov <firstname.lastname@example.org>||Thu Oct 17 17:19:53 2019 -0400|
|committer||Dmitri Shuralyov <email@example.com>||Thu Oct 17 22:01:48 2019 +0000|
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 <firstname.lastname@example.org>
This repository holds the Go Website server code and content.
The easiest way to install is to run
go get -u golang.org/x/website. You can also manually git clone the repository to
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.