blog: update README.md for new cloud build process

Change-Id: I270365170c5871526901df519bba9d5b3819fae3
Reviewed-on: https://go-review.googlesource.com/c/blog/+/321670
Trust: Russ Cox <rsc@golang.org>
Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
1 file changed
tree: eff885a81ac4d349dd6d71c21ea90f3fb1190778
  1. .gcloudignore
  2. .gitattributes
  3. AUTHORS
  4. CONTRIBUTING.md
  5. CONTRIBUTORS
  6. LICENSE
  7. PATENTS
  8. README.md
  9. _content/
  10. _static/
  11. _template/
  12. app.yaml
  13. appengine.go
  14. blog.go
  15. codereview.cfg
  16. go.mod
  17. go.sum
  18. local.go
  19. local_test.go
  20. rewrite.go
README.md

Go Blog

Go Reference

This repository holds the Go Blog server code and content.

Download/Install

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.

Running Locally

To run the blog server locally:

go run . -reload

and then visit http://localhost:8080/ in your browser.

Contributing

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.

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 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.

Deploying

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:

  1. 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]
    
  2. Copy that URL and load it in your browser. Check that it looks OK.

  3. 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.

  4. You're done.