Those can still be useful as a disaster recovery mechanism.

This reverts commit deb01b7293ca44285e43ab80b5f2470175d45ed6.

service/static-shim.md

@@ -310,6 +310,32 @@ pages:
     - merge_requests
 ```
 
+## Deploy artifacts manually
+
+If a site is not deploying normally, it's still possible to deploy a
+site by hand by downloading and extracting the artifacts using the
+`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
+tell the puller to deploy in debugging mode with this command:
+
+    sudo -u static-gitlab-shim /usr/local/bin/static-gitlab-shim-pull --artifacts-url https://gitlab.torproject.org/tpo/tpa/status-site/-/jobs/38077/artifacts/download --site-url status.torproject.org --debug
+
+The `--artifacts-url` is the `Download` link in the job page. This
+will:
+ 
+ 1. download the artifacts (which is a ZIP file)
+ 2. extract them in a temporary directory
+ 3. `rsync --checksum` them to the actual source directory (to avoid
+    spurious timestamp changes)
+ 4. call `static-update-component` to deploy the site
+
+Note that this script was part of the webhook implementation and might
+eventually be retired if that implementation is completely
+removed. This logic now lives in the [`static-shim-deploy.yml`
+template][].
+
+
 ## Converting a job from Jenkins
 
 NOTE: this shouldn't be necessary anymore, as Jenkins was retired at