1d4d2693ba
Experiments extracted from GOEXPERIMENT were not being passed to vet. Some experiments, such as aliastypeparams, affect vet as well, and so must be set in the vet environment. Change-Id: I7d72c50f5237753b84d26a27fbb09d9bfcf34626 Reviewed-on: https://go-review.googlesource.com/c/playground/+/612456 Reviewed-by: Robert Griesemer <gri@google.com> Auto-Submit: Robert Findley <rfindley@google.com> LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com> Reviewed-by: Tim King <taking@google.com> |
||
|---|---|---|
| cmd | ||
| deploy | ||
| examples | ||
| internal | ||
| sandbox | ||
| static | ||
| testdata/p | ||
| .gitignore | ||
| CONTRIBUTING.md | ||
| Dockerfile | ||
| LICENSE | ||
| Makefile | ||
| PATENTS | ||
| README.md | ||
| app.go2go.yaml | ||
| app.goprev.yaml | ||
| app.gotip.yaml | ||
| app.yaml | ||
| cache.go | ||
| client.go | ||
| codereview.cfg | ||
| edit.go | ||
| edit.html | ||
| enable-fake-time.patch | ||
| examples.go | ||
| fake_fs.lst | ||
| fmt.go | ||
| fmt_test.go | ||
| go.mod | ||
| go.sum | ||
| logger.go | ||
| main.go | ||
| metrics.go | ||
| play.go | ||
| play_test.go | ||
| sandbox.go | ||
| sandbox_test.go | ||
| server.go | ||
| server_test.go | ||
| share.go | ||
| store.go | ||
| tests.go | ||
| txtar.go | ||
| txtar_test.go | ||
| version.go | ||
| vet.go | ||
README.md
playground
This subrepository holds the source for the Go playground: https://go.dev/play/
Building
# build the image
docker build -t golang/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
To run the "gotip" version of the playground, set GOTIP=true
in your environment (via -e GOTIP=true if using docker run).
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.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
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.