| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
|
|
| |
Using go run does not leave a binary in the working directory.
This is possible now that golang.org/issue/22726 is resolved.
Change-Id: I63cd28bdb66673262fa45e56dc2e8ac39a0fa1a7
Reviewed-on: https://go-review.googlesource.com/c/blog/+/216657
Reviewed-by: Robert Griesemer <gri@golang.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When deployed with App Engine on blog.golang.org,
insert analytics HTML at the beginning of <head>.
Add deploy instructions to the README.
Also update to the App Engine Go 1.12 runtime.
Change-Id: Icf0919fd22d80cb8cb765845acd1d72f85f11fa1
Reviewed-on: https://go-review.googlesource.com/c/blog/+/198337
Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org>
TryBot-Result: Gobot Gobot <gobot@golang.org>
Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
|
| |
|
|
|
|
|
| |
Change-Id: Id2944b4338c0abda50996e3c885ce1bddba9ab68
Reviewed-on: https://go-review.googlesource.com/c/blog/+/190117
Reviewed-by: Jean de Klerk <deklerk@google.com>
Reviewed-by: Jay Conrod <jayconrod@google.com>
|
| |
|
|
|
|
|
|
|
|
| |
Additionally makes some small changes to abide by best practices.
Updates golang/go#9936
Change-Id: I88263ef78548365b3cfb3f14bae48deb01d30f4f
Reviewed-on: https://go-review.googlesource.com/c/blog/+/189457
Reviewed-by: Katie Hockman <katie@golang.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Clearly the main server had run ahead of the local one.
The local one was expecting requests to say /static/,
which they do not, and there are also requests from
two different static file locations, not just one.
Now when you run the local blog server you see all
the styling of the blog site instead of unstyled HTML.
Also update README.md.
Change-Id: Ia662419339cd7546f0611f1b896c343902a018d5
Reviewed-on: https://go-review.googlesource.com/c/155019
Run-TryBot: Russ Cox <rsc@golang.org>
TryBot-Result: Gobot Gobot <gobot@golang.org>
Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
+ 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>
|
|
|
Move the README to README.md so Gerrit can render it; currently
Gerrit only renders files named exactly "README.md" (for example at
https://go.googlesource.com/go).
Add more links to the README explaining how to file issues,
how to submit code changes, where to download the code to and
how to get it. Hopefully this should help people who go to
https://go.googlesource.com/blog or https://github.com/golang/blog
figure out how to get started with development.
Add a link in the footer to the source code for the blog, so people
know where to find it.
Updates golang/go#21038.
Updates golang/go#21034.
Change-Id: Ie378cf2aa42f56485b5d5c9a943f5b9957d96371
Reviewed-on: https://go-review.googlesource.com/49291
Reviewed-by: Russ Cox <rsc@golang.org>
|