commit | d4a18cb3f6b647e4c655be819ae20ba8559371c7 | [log] [tgz] |
---|---|---|
author | Jamal Carvalho <jamal@golang.org> | Sat Dec 18 02:28:40 2021 +0000 |
committer | Jamal Carvalho <jamalcarvalho@google.com> | Tue Dec 21 00:00:05 2021 +0000 |
tree | 10a9aef7c2c8561f62745116000bf14710247a43 | |
parent | dc956758886941601506bda61e3ab50672d747ea [diff] |
cmd,internal: add ability to cache screenshots for an origin server To speed up subsequent test runs or for use in CI testing screenshots can be cached for an origin server by adding the ::cache suffix to the URL. For example, https://go.dev::cache. Change-Id: I6ae6fd3f8f6f9fe884f74af6fb9ec7e6666e2f8b Reviewed-on: https://go-review.googlesource.com/c/website/+/373477 Run-TryBot: Jamal Carvalho <jamal@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Jonathan Amsterdam <jba@google.com> Trust: Jamal Carvalho <jamalcarvalho@google.com>
This repo holds content and serving programs for the go.dev and golang.org web sites.
Content is in _content/ (go.dev) and tour/ (go.dev/tour). Server code is in cmd/ and internal/.
To run the combined go.dev+golang.org server to preview local content changes, use:
go run ./cmd/golangorg
The supporting programs cmd/admingolangorg and cmd/googlegolangorg are the servers for admin.golang.org and google.golang.org. (They do not use the _content/ directories.)
Each command directory has its own README.md explaining deployment.
This repository uses prettier to format JS and CSS files.
See also:
The version of prettier
used is 1.18.2.
It is encouraged that all JS and CSS code be run through this before submitting a change. However, it is not a strict requirement enforced by CI.
Each time a CL is reviewed and submitted, the code is deployed to App Engine. See cmd/golangorg/README.md for details.
This repository uses Gerrit for code changes. To learn how to submit changes to this repository, see https://go.dev/doc/contribute.
The main issue tracker for the website repository is located at https://github.com/golang/go/issues. Prefix your issue with “x/website:” in the subject line, so it is easy to find.