Point the "environment" at a more productive URL and explain this

.gitlab-ci.yml

@@ -88,8 +88,17 @@ update-staging:
   only:
     - "staging"
   environment:
+    # You can find some status information about environments in GitLab at
+    # https://whetstone.privatestorage.io/privatestorage/PrivateStorageio/-/environments.
     name: "staging"
-    url: "https://privatestorage-staging.com/"
+    # The URL controls where the "View Deployment" button for this environment
+    # will take you.  The main website isn't controlled by this codebase so we
+    # don't point there.  The monitoring system *is* controlled by this
+    # codebase and it also tells us lots of stuff about other things
+    # controlled by this codebase so that seems like a good place to land.
+    # Not that I make it a habit to visit the deployment using the GitLab
+    # button...  Still, discoverability or something.
+    url: "https://monitoring.privatestorage-staging.com/"
 
 # Update the production deployment - only on a merge to the production branch.
 deploy-to-production:
@@ -97,5 +106,6 @@ deploy-to-production:
   only:
     - "production"
   environment:
+    # See notes in `update-staging`.
     name: "production"
-    url: "https://private.storage/"
+    url: "https://monitoring.private.storage/"