|author||Andrew Gerrand <firstname.lastname@example.org>||Wed Aug 09 17:32:50 2017 +1000|
|committer||Andrew Gerrand <email@example.com>||Wed Aug 09 22:04:22 2017 +0000|
cloud/autocert: don't import autocert; use names from cloud/https The upspin.io repository vendors the golang.org/x/crypto/acme/autocert package, so when the autocert package in this repository imported the autocert package from x/crypto, it was seeing a different package. By using these types exported from the cloud/https package, the sentinel error value ErrAutocertCacheMiss will be equivalent to the one that the vendored x/crypto/acme/autocert package expects. Without this change, renewing of Let's Encrypt certs was silently broken. This workaround will go away once we have resolved issue upspin/upspin#214. Change-Id: Iccc831a0cdf80d5a310fa278ea9b518daf669f5d Reviewed-on: https://upspin-review.googlesource.com/11960 Reviewed-by: Rob Pike <firstname.lastname@example.org>
See the Setting up upspinserver document for information about running an Upspin service that stores its data in Google Cloud Storage.
See the Deploying Upspin servers to Google Cloud Platform document for information about running an Upspin cluster on Google Container Engine.
See the master repository for more information about the Upspin project.