| Name | Date | Size | #Lines | LOC | ||
|---|---|---|---|---|---|---|
| .. | - | - | ||||
| .gcloudignore | H A D | 25-Apr-2025 | 31 | 3 | 3 | |
| README.md | H A D | 25-Apr-2025 | 608 | 16 | 11 | |
| app.yaml | H A D | 25-Apr-2025 | 91 | 6 | 5 | |
| deploy | H A D | 25-Apr-2025 | 1.3 KiB | 50 | 25 | |
| main.py | H A D | 25-Apr-2025 | 3.2 KiB | 97 | 63 | |
| requirements.txt | H A D | 25-Apr-2025 | 34 | 3 | 2 |
README.md
1# www.perfetto.dev Cloud scripts 2 3The docs site follows the same architecture of ui.perfetto.dev. 4See [go/perfetto-ui-autopush](http://go/perfetto-ui-autopush) for docs. 5 6## /appengine : GAE <> GCS proxy 7 8The Google AppEngine instance that responds to www.perfetto.dev. 9It simply passes through the requests to the bucket gs://perfetto.dev . 10This should NOT be re-deployed when uploading new docs, as the actual 11artifacts live in GCS. 12 13We are using AppEngine for historical reasons, at some point this should 14be migrated to a Type 7 Google Cloud Load Balancer, which supports 15direct backing by a GCS bucket. 16