| Commit message (Collapse) | Author | Age | |
|---|---|---|---|
| * | blog: remove all remaining protocol-relative URLs | Chris Broadfoot | 2018-12-20 |
| | | | | | | | | | | | | | | | | | Protocol-relative URLs (e.g., "//blog.golang.org") were previously removed in the content of the blog, but not in other areas. Notably, in the atom feed. This causes feed reader apps to fail, because it doesn't know to use https for those URLs. Always use the https scheme, including in the atom feed as well as a couple remaining places in the blog template. Fixes golang/go#17961 Change-Id: I694c888de9437937ba1910227ddae42d3eb0405c Reviewed-on: https://go-review.googlesource.com/c/155357 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org> | ||
| * | blog: clean up blog to allow usage with gcloud command | Andrew Bonventre | 2018-05-24 |
| + The app.yaml file needs to be in the same directory as the entry-point Go files, so those are moved from ./blog to ./ + Go files within the context article did not have the +build OMIT directive, so gcloud would view them as files that needed to be built at deploy time. Add the +build OMIT directive and use the context package instead of x/net/context. + Switch to using a service instead of version and update app.yaml to account for this. + Use 1.9 as the runtime. + Remove superfluous .gitignore Change-Id: I7c886849b912bc7f5b67cd2791cb6986d93d5cc7 Reviewed-on: https://go-review.googlesource.com/114455 Reviewed-by: Russ Cox <rsc@golang.org> | |||