| commit | 9dd3d9b97af3dba2bd18f1a5e18bd8e8edf78962 | [log] [tgz] |
|---|---|---|
| author | Russ Cox <rsc@golang.org> | Mon Mar 09 23:19:59 2020 -0400 |
| committer | Russ Cox <rsc@golang.org> | Wed Mar 11 14:10:15 2020 +0000 |
| tree | 700ba48e63519a9b9bfcfef1aa783ca7e1f821a3 | |
| parent | 482079d678d84e207dd9ae63266c4bd4e653886b [diff] |
content: use tabs consistently for code blocks + indentation A few articles used four spaces instead. The present format will convert to four spaces for indentation on its own; use tabs. The present format does not care what indentation is used, but use tabs everywhere for consistency. For golang/go#33955. Change-Id: I2bab8aa72fa2f68d48fb833b7317f87d7624a05f Reviewed-on: https://go-review.googlesource.com/c/blog/+/222840 Reviewed-by: Ian Lance Taylor <iant@golang.org>
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.
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.