playground: slurp binary to memory in gvisor mode

Slurp the binary to memory before POSTing it. This simplifies retries
a bit (doesn't need to re-open the file) and sets a Content-Length
header, and checks the file size early, rather than having the backend
complain.

None of this should matter for correctness (and unnecessarily uses
more memory than before), but we're sometimes seeing timeout errors
followed by this frontend returning (and caching!) an empty response
where the backend never sees a binary arrive, so this is somewhat a
shot in the dark for now. Something's up with our internal load
balancer, perhaps. Still debugging.

Also update/add some comments.

Updates golang/go#25224

Change-Id: I12f08db8ac77743b555fe7ef56bccf8cbc45742c
Reviewed-on: https://go-review.googlesource.com/c/playground/+/215058
Reviewed-by: Alexander Rakoczy <alex@golang.org>
1 file changed
tree: acc8cd2d7a43ac5ef20ed6b3d93dbc334d0cc847
  1. .gitignore
  2. AUTHORS
  3. CONTRIBUTING.md
  4. CONTRIBUTORS
  5. Dockerfile
  6. LICENSE
  7. Makefile
  8. PATENTS
  9. README.md
  10. app.yaml
  11. cache.go
  12. client.go
  13. cmd/
  14. codereview.cfg
  15. deploy/
  16. edit.go
  17. edit.html
  18. enable-fake-time.patch
  19. fake_fs.lst
  20. fmt.go
  21. fmt_test.go
  22. go.mod
  23. go.sum
  24. logger.go
  25. main.go
  26. play.go
  27. play_test.go
  28. sandbox.go
  29. sandbox/
  30. server.go
  31. server_test.go
  32. share.go
  33. static/
  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.