Skip to content

Commit b884d85

Browse files
committed
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 <[email protected]> Reviewed-by: Brad Fitzpatrick <[email protected]>
1 parent be0fe03 commit b884d85

File tree

1 file changed

+8
-0
lines changed

1 file changed

+8
-0
lines changed

README.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -20,6 +20,14 @@ cat /path/to/code.go | go run client.go | curl -s --upload-file - localhost:8080
2020

2121
# Deployment
2222

23+
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):
24+
25+
```
26+
gcloud config set app/cloud_build_timeout 1200 # 20 mins
27+
```
28+
29+
Then:
30+
2331
```
2432
gcloud --project=golang-org [email protected] app deploy app.yaml
2533
```

0 commit comments

Comments
 (0)