| OLD | NEW |
| 1 # appengine/ | 1 # appengine/ |
| 2 | 2 |
| 3 This directory contains the AppEngine services needed for a LUCI infrastructure. | 3 This directory contains the AppEngine services needed for a LUCI infrastructure. |
| 4 | 4 |
| 5 Every single microservice below is _optional_. Please mix and match based on | 5 Every single microservice below is _optional_. Please mix and match based on |
| 6 your needs. | 6 your needs. |
| 7 | 7 |
| 8 | 8 |
| 9 ## TL;DR | 9 ## TL;DR |
| 10 | 10 |
| (...skipping 36 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
| 47 third parties that are not meant to be ever used on a AppEngine server. | 47 third parties that are not meant to be ever used on a AppEngine server. |
| 48 | 48 |
| 49 | 49 |
| 50 ## Tooling | 50 ## Tooling |
| 51 | 51 |
| 52 All services can be managed with `./tools/gae`, including running locally or | 52 All services can be managed with `./tools/gae`, including running locally or |
| 53 pushing a new version. Use `./tools/gae help` for an up to date list of commands | 53 pushing a new version. Use `./tools/gae help` for an up to date list of commands |
| 54 available. | 54 available. |
| 55 | 55 |
| 56 | 56 |
| 57 ### Pushing |
| 58 |
| 59 Pushing new code to an AppEngine instance doesn't change the default version. |
| 60 |
| 61 To push a new version of one of the services, do: |
| 62 |
| 63 ``` |
| 64 cd <server> # for example, config_service |
| 65 ./tools/gae upload -A <instance_name> |
| 66 ``` |
| 67 |
| 68 As described in the output by the tool, you can access it to |
| 69 `<version>-dot-<name>.appspot.com` until you switch the default version. |
| 70 |
| 71 |
| 72 ### Changing the version |
| 73 |
| 74 To make the new code _live_, you need to change the default version: |
| 75 |
| 76 ``` |
| 77 cd <server> # for example, config_service |
| 78 ./tools/gae switch -A <instance_name> |
| 79 ``` |
| 80 |
| 81 `gae` will propose the versions already uploaded and will propose the latest one |
| 82 by default. |
| 83 |
| 84 |
| 57 ## External dependencies | 85 ## External dependencies |
| 58 | 86 |
| 59 luci-py leverages Chromium specific functionalities: | 87 luci-py leverages Chromium specific functionalities: |
| 60 [CIPD](https://chromium.googlesource.com/infra/infra/+/master/cipd/) | 88 [CIPD](https://chromium.googlesource.com/infra/infra/+/master/cipd/) |
| 61 (hermetic package management) and | 89 (hermetic package management) and |
| 62 [ts_mon](https://chromium.googlesource.com/infra/infra/+/master/infra_libs/ts_mo
n/) | 90 [ts_mon](https://chromium.googlesource.com/infra/infra/+/master/infra_libs/ts_mo
n/) |
| 63 (monitoring). Neither are strictly required for operational purpose. | 91 (monitoring). Neither are strictly required for operational purpose. |
| OLD | NEW |