document how to ressurect status.torproject.org

service/status.md

@@ -166,9 +166,37 @@ Then, of course, DNS needs to be updated to point there.
 A site could also be deployed on *another* GitLab server with "GitLab
 pages" enabled. For example, if the repository is pushed to
 <https://gitlab.com/>, the GitLab CI/CD system there will
-automatically pick it up and publish it.
+automatically pick up the configuration and run it.
 
-Then DNS needs to be tweaked to point there as well.
+Unfortunately, due to the heavy customization we used to deploy the
+site to the static mirror system, the stock `.gitlab-ci.yml` file will
+likely not work on another system. An alternate `.gitlab-ci-pages.yml`
+file should be available in the Git repository and can be activated in
+the GitLab project in Settings -> CI/CD -> CI/CD configuration file.
+
+That should give you a "test" GitLab pages site with a URL like:
+
+    https://user.gitlab.io/tpa-status/
+
+To transfer the real site there, you need to go into the project's
+Settings -> Pages section and hit `New Domain`. 
+
+Enter `status.torproject.org` there, which will ask you to add an
+`TXT` record in the `torproject.org` zone. 
+
+Add the `TXT` record to `domains.git/torproject.org`, commit and push,
+then hit the "Retry verification" button in the GitLab interface.
+
+Once the domain is verified, point the `status.torproject.org` domain
+to the new backend:
+
+    status CNAME user.gitlab.io
+
+For example, in my case, it was:
+
+    status CNAME anarcat.gitlab.io
+
+See also the [upstream documentation](https://docs.gitlab.com/ee/user/project/pages/custom_domains_ssl_tls_certification/index.html) for details.
 
 # Reference