x/playground: remove -mod=mod and execute go mod tidy before command

Previously, `-mod=mod` was included to pull down dependencies.
This change executes go mod tidy before building packages, that will
allow for go work usage, and address golang/go#40728

Fixes golang/go#54741

Change-Id: I66affc8d2a2e72d958415ea1c052dd3dcf38841e
Reviewed-on: https://go-review.googlesource.com/c/playground/+/458895
Reviewed-by: Robert Findley <rfindley@google.com>
Auto-Submit: Bryan Mills <bcmills@google.com>
Reviewed-by: Matthew Dempsky <mdempsky@google.com>
Commit-Queue: Bryan Mills <bcmills@google.com>
TryBot-Result: Gopher Robot <gobot@golang.org>
Run-TryBot: Bryan Mills <bcmills@google.com>
Reviewed-by: Bryan Mills <bcmills@google.com>
4 files changed
tree: 34791589151975065689357929fdf98323c900cf
  1. cmd/
  2. deploy/
  3. examples/
  4. internal/
  5. sandbox/
  6. static/
  7. .gitignore
  8. app.go2go.yaml
  9. app.goprev.yaml
  10. app.gotip.yaml
  11. app.yaml
  12. cache.go
  13. client.go
  14. codereview.cfg
  16. Dockerfile
  17. edit.go
  18. edit.html
  19. enable-fake-time.patch
  20. examples.go
  21. fake_fs.lst
  22. fmt.go
  23. fmt_test.go
  24. go.mod
  25. go.sum
  27. logger.go
  28. main.go
  29. Makefile
  30. metrics.go
  31. mod.go
  33. play.go
  34. play_test.go
  35. README.md
  36. sandbox.go
  37. sandbox_test.go
  38. server.go
  39. server_test.go
  40. share.go
  41. store.go
  42. tests.go
  43. txtar.go
  44. txtar_test.go
  45. version.go
  46. vet.go


Go Reference

This subrepository holds the source for the Go playground: https://go.dev/play/


# build the image
docker build -t golang/playground .


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

To run the “gotip” version of the playground, set GOTIP=true in your environment (via -e GOTIP=true if using docker run).


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.yaml, deploy/playground_trigger.yaml, and deploy/deploy.json.

Changes to the trigger configuration can be made to the YAML files, or in the GCP UI, which should be kept in sync using the push-cloudbuild-triggers and pull-cloudbuild-triggers make targets.

Deploy via Cloud Build

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

gcloud --project=golang-org builds submit --config deploy/deploy.json .

To deploy the “Go tip” version of the playground, which uses the latest development build, use deploy_gotip.json instead:

gcloud --project=golang-org builds submit --config deploy/deploy_gotip.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


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


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