Google Git
Sign in
go / playground / 0eefa27dcbc5bab25c7ce1c50baf6e504f783bf8
commit0eefa27dcbc5bab25c7ce1c50baf6e504f783bf8[log] [tgz]
authorBrad Fitzpatrick <bradfitz@golang.org>Tue Jan 14 20:01:12 2020 +0000
committerBrad Fitzpatrick <bradfitz@golang.org>Tue Jan 14 20:08:23 2020 +0000
tree958bb0e4c63bbaff99ed917444c04695cf3e0fe6
parent62f81bd9157bf7f29142fc0030f1a7a62bd68edd [diff]
sandbox: create larger VMs, add instance tags to permits health checks

The GCP VMs were "failing" health checks before due to the firewall not
allowing GCP's health checks.

Added, per https://cloud.google.com/load-balancing/docs/health-checks#firewall_rules

I just added both types of firewall rules (for legacy and non-legacy)
so we can adjust which type of health checks we use in the future.

Updates golang/go#25224

Change-Id: Ie8e585f76d97e770f1993b945e7a53732aec2cb8
Reviewed-on: https://go-review.googlesource.com/c/playground/+/214681
Reviewed-by: Alexander Rakoczy <alex@golang.org>
1 file changed
tree: 958bb0e4c63bbaff99ed917444c04695cf3e0fe6
  1. cmd/
  2. deploy/
  3. sandbox/
  4. static/
  5. .gitignore
  6. app.yaml
  7. AUTHORS
  8. cache.go
  9. client.go
  10. codereview.cfg
  11. CONTRIBUTING.md
  12. CONTRIBUTORS
  13. Dockerfile
  14. edit.go
  15. edit.html
  16. enable-fake-time.patch
  17. fake_fs.lst
  18. fmt.go
  19. fmt_test.go
  20. go.mod
  21. go.sum
  22. LICENSE
  23. logger.go
  24. main.go
  25. Makefile
  26. PATENTS
  27. play.go
  28. play_test.go
  29. README.md
  30. sandbox.go
  31. server.go
  32. server_test.go
  33. share.go
  34. store.go
  35. tests.go
  36. txtar.go
  37. txtar_test.go
  38. vet.go
README.md

playground

This subrepository holds the source for the Go playground: https://play.golang.org/

Building

# build the image
docker build -t playground .

Running

docker run --name=play --rm -p 8080:8080 golang/playground &
# run some Go code
cat /path/to/code.go | go run client.go | curl -s --upload-file - localhost:8080/compile

Deployment

Deployment Triggers

Playground releases automatically triggered when new Go repository tags are pushed to GitHub, or when master is pushed on the playground repository.

For details, see deploy/go_trigger.json, deploy/playground_trigger.json, and deploy/deploy.json.

After making changes to trigger configuration, update configuration by running the following Make target:

make update-cloudbuild-trigger

Deploy via Cloud Build

The Cloud Build configuration will always build and deploy with the latest supported release of Go.

gcloud builds submit --config deploy/deploy.json .

Deploy via gcloud app deploy

Building the playground Docker container takes more than the default 10 minute time limit of cloud build, so increase its timeout first (note, app/cloud_build_timeout is a global configuration value):

gcloud config set app/cloud_build_timeout 1200  # 20 mins

Alternatively, to avoid Cloud Build and build locally:

make docker
docker tag golang/playground:latest gcr.io/golang-org/playground:latest
docker push gcr.io/golang-org/playground:latest
gcloud --project=golang-org --account=you@google.com app deploy app.yaml --image-url=gcr.io/golang-org/playground:latest

Then:

gcloud --project=golang-org --account=you@google.com app deploy app.yaml

Contributing

To submit changes to this repository, see https://golang.org/doc/contribute.html.