playground: allow explicit GOPROXY variable

Setting the PLAY_GOPROXY variable of the playground modifies where
the playground fetches module information from.  This allows users to
install the playground inside their company VPN and use private modules.

The variable isn't named "GOPROXY" to not confuse which context the URL
is used for.  The name PLAY_* is adopted from the existing env variable
ALLOW_PLAY_MODULE_DOWNLOADS.

Fixes golang/go#32740

Change-Id: Idcd0530c1c28342414e0bc5439fca6a2272e1eaa
Reviewed-on: https://go-review.googlesource.com/c/playground/+/184558
Reviewed-by: Andrew Bonventre <andybons@golang.org>
3 files changed
tree: 573973dd4f677a4639a4c728a24f614476773a61
  1. AUTHORS
  2. CONTRIBUTING.md
  3. CONTRIBUTORS
  4. Dockerfile
  5. LICENSE
  6. Makefile
  7. PATENTS
  8. README.md
  9. app.yaml
  10. cache.go
  11. client.go
  12. cmd/
  13. codereview.cfg
  14. deploy/
  15. edit.go
  16. edit.html
  17. enable-fake-time.patch
  18. fake_fs.lst
  19. fmt.go
  20. fmt_test.go
  21. go.mod
  22. go.sum
  23. logger.go
  24. main.go
  25. play.go
  26. play_test.go
  27. sandbox.go
  28. server.go
  29. server_test.go
  30. share.go
  31. static/
  32. store.go
  33. tests.go
  34. txtar.go
  35. txtar_test.go
  36. 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 -d -p 8080:8080 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 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.