commit | 97ded1e093da2a216dd3c479bdb3846e0976d52a | [log] [tgz] |
---|---|---|
author | Ainar Garipov <ainar-g@yandex.ru> | Fri Nov 08 20:05:14 2019 +0300 |
committer | Bryan C. Mills <bcmills@google.com> | Fri Nov 15 21:00:52 2019 +0000 |
tree | d10c7f8cf176558a3403424e40f134692c428de2 | |
parent | 3780780ce6687dee167c70df957fc959fa96afda [diff] |
content: ensure better semver versions in the v2 modules article The Semantic Versioning specification at https://semver.org uses dots to separate the numeric part of a pre-release version from the non-numeric to ensure that they sort correctly. Make the article comply. Change-Id: I7a366e4c180f5048b1cc19cdf3e66c515989e4ab Reviewed-on: https://go-review.googlesource.com/c/blog/+/206157 Reviewed-by: Jean de Klerk <deklerk@google.com> Reviewed-by: Jay Conrod <jayconrod@google.com> Reviewed-by: Bryan C. Mills <bcmills@google.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 build && ./blog -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.
To deploy blog.golang.org, run:
GO111MODULE=on gcloud --project=golang-org app deploy --no-promote app.yaml
This will create a new version, which can be viewed within the golang-org GCP project.
Check that the deployed version looks OK (click the version link in GCP).
If all is well, click “Migrate Traffic” to move 100% of the blog.golang.org traffic to the new version.
You're done.