all: mv content _content; mv template _template

Moving these into underscore directories
hides them from "go mod tidy",
which otherwise wants to add a dependency
on gorilla for content/context/*.go.

Also update appengine.go and local.go
to know about new locations.

Change-Id: I7e1eaee7aaa971ee39c6c0e3cca475086443fbae
Reviewed-on: https://go-review.googlesource.com/c/blog/+/296369
Trust: Russ Cox <rsc@golang.org>
Run-TryBot: Russ Cox <rsc@golang.org>
TryBot-Result: Go Bot <gobot@golang.org>
Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
777 files changed
tree: eed62c196febbc35461d87d944af2f13d1002055
  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
  21. support/
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

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

  2. Check that the deployed version looks OK (click the version link in GCP).

  3. If all is well, click “Migrate Traffic” to move 100% of the blog.golang.org traffic to the new version.

  4. You're done.