|author||Dmitri Shuralyov <firstname.lastname@example.org>||Thu Feb 28 13:47:27 2019 -0500|
|committer||Dmitri Shuralyov <email@example.com>||Mon Mar 04 18:09:06 2019 +0000|
README: document the need to increase cloud build timeout It's unfortunate to introduce an extra step of setting a global configuration value to the deploy process. It would be better if this could be an application-scoped setting specified in the app.yaml configuration. However, that doesn't seem to be possible, and after reading through documentation and waiting to hear any suggestions at golang/go#28046, I have not become aware of a better solution. Document this approach for now, and if we learn of a better solution in the future, this can be improved then. Fixes golang/go#28046 Change-Id: I2e9b7bbd38aa8313ff6eab0bf99dd2fe48f57544 Reviewed-on: https://go-review.googlesource.com/c/playground/+/164577 Reviewed-by: Andrew Bonventre <firstname.lastname@example.org> Reviewed-by: Brad Fitzpatrick <email@example.com>
This subrepository holds the source for the Go playground: https://play.golang.org/
# build the image docker build -t playground .
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
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
gcloud --project=golang-org --firstname.lastname@example.org app deploy app.yaml
To submit changes to this repository, see https://golang.org/doc/contribute.html.