clarification authored by anarcat's avatar anarcat
...@@ -226,8 +226,8 @@ pages: ...@@ -226,8 +226,8 @@ pages:
## Deploy artifacts manually ## Deploy artifacts manually
If a site is not deploying normally, it's possible to deploy a site by If a site is not deploying normally, it's still possible to deploy a
hand by downloading and extracting the artifacts using the site by hand by downloading and extracting the artifacts using the
`static-gitlab-shim-pull` script. `static-gitlab-shim-pull` script.
For example, given the [Pipeline 13285](https://gitlab.torproject.org/tpo/tpa/status-site/-/pipelines/13285) has [job 38077](https://gitlab.torproject.org/tpo/tpa/status-site/-/jobs/38077), we can For example, given the [Pipeline 13285](https://gitlab.torproject.org/tpo/tpa/status-site/-/pipelines/13285) has [job 38077](https://gitlab.torproject.org/tpo/tpa/status-site/-/jobs/38077), we can
...@@ -244,8 +244,10 @@ will: ...@@ -244,8 +244,10 @@ will:
spurious timestamp changes) spurious timestamp changes)
4. call `static-update-component` to deploy the site 4. call `static-update-component` to deploy the site
Note that this script is part of the webhook implementation and might Note that this script was part of the webhook implementation and might
eventually be retired if that implementation is completely removed. eventually be retired if that implementation is completely
removed. This logic now lives in the [`static-shim-deploy.yml`
template][].
## Pager playbook ## Pager playbook
... ...
......