|author||Russ Cox <email@example.com>||Tue May 25 20:22:20 2021 -0400|
|committer||Russ Cox <firstname.lastname@example.org>||Wed May 26 00:23:40 2021 +0000|
README.md: fix link Change-Id: If95523697fe41cd0856abb156c6aeb6cd1f52ddf Reviewed-on: https://go-review.googlesource.com/c/blog/+/322749 Trust: Russ Cox <email@example.com> Run-TryBot: Russ Cox <firstname.lastname@example.org> Reviewed-by: Russ Cox <email@example.com>
This repository holds the Go Blog server code and content.
The easiest way to install is to run
go get -u golang.org/x/blog. You can also manually git clone the repository to $GOPATH/src/golang.org/x/blog.
To run the blog server locally:
go run . -reload
and then visit http://localhost:8080/ in your browser.
Articles are written in the x/tools/present format. Articles on the blog should have broad interest to the Go community, and are mainly written by Go contributors. We encourage you to share your experiences using Go on your own website, and to share them with the Go community. Hugo is a static site server written in Go that makes it easy to write and share your stories.
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 blog is located at https://github.com/golang/go/issues. Prefix your issue with “x/blog:” in the subject line, so it is easy to find.
The Google Cloud project triggers a fresh deploy of the blog on each submit but that deployment is published to a temporary URL.
To publish the blog to blog.golang.org, you need access to the Cloud Console for the golang-org project. Then:
Visit the builds list and click on the build hash for the most recent build with trigger name “Redeploy-blog-on-blog-commit”.
Scrolling to the bottom of the build log, you will find a URL in a log message like
Deployed service [blog] to [https://TEMPORARYURL.appspot.com]
Copy that URL and load it in your browser. Check that it looks OK.
Assuming it does, visit the AppEngine versions list. Click “Migrate Traffic” on the new entry to move 100% of the blog.golang.org traffic to the new version.