blog: clean up blog to allow usage with gcloud command

+ The app.yaml file needs to be in the same directory as the
  entry-point Go files, so those are moved from ./blog to ./
+ Go files within the context article did not have the +build OMIT
  directive, so gcloud would view them as files that needed to be
  built at deploy time. Add the +build OMIT directive and use
  the context package instead of x/net/context.
+ Switch to using a service instead of version and update app.yaml
  to account for this.
+ Use 1.9 as the runtime.
+ Remove superfluous .gitignore

Change-Id: I7c886849b912bc7f5b67cd2791cb6986d93d5cc7
Reviewed-on: https://go-review.googlesource.com/114455
Reviewed-by: Russ Cox <rsc@golang.org>
11 files changed
tree: c05463ed903c6790b1b403b6ebc05ab95875ce8f
  1. .gitattributes
  2. AUTHORS
  3. CONTRIBUTING.md
  4. CONTRIBUTORS
  5. LICENSE
  6. PATENTS
  7. README.md
  8. app.yaml
  9. appengine.go
  10. blog.go
  11. codereview.cfg
  12. content/
  13. local.go
  14. local_test.go
  15. rewrite.go
  16. static/
  17. support/
  18. template/
README.md

Go Blog

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:

dev_appserver.py app.yaml

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

Contributing

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 “blog:” in the subject line, so it is easy to find.