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. AUTHORS
  7. CONTRIBUTING.md
  8. CONTRIBUTORS
  9. Dockerfile
  10. LICENSE
  11. Makefile
  12. PATENTS
  13. README.md
  14. app.yaml
  15. cache.go
  16. client.go
  17. codereview.cfg
  18. edit.go
  19. edit.html
  20. enable-fake-time.patch
  21. fake_fs.lst
  22. fmt.go
  23. fmt_test.go
  24. go.mod
  25. go.sum
  26. logger.go
  27. main.go
  28. play.go
  29. play_test.go
  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.