The Go Playground

Clone this repo:


  1. bd57f61 playground: bound compilation time too by Brad Fitzpatrick · 5 weeks ago master
  2. 394f19f playground: differentiate cache key based on client JS version by Brad Fitzpatrick · 5 months ago
  3. a712dec Dockerfile: update Go version to 1.13 by Andrew Bonventre · 6 weeks ago
  4. ee0783d playground: set GOPROXY when building Docker image by Andrew Bonventre · 3 months ago
  5. 509e10f playground: allow explicit GOPROXY variable by Jack Lindamood · 4 months ago


This subrepository holds the source for the Go playground:


# build the image
docker build -t 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


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
docker push
gcloud --project=golang-org app deploy app.yaml


gcloud --project=golang-org app deploy app.yaml


To submit changes to this repository, see