proxies: stg.release-monitoring.org make this it's own site

Normally we can just define the site once with it's prod name and use
that in stg with an alias. This works because we have a wildcard ssl
cert for *.fedoraproject.org. So, stg.fedoraproject.org and
fedoraproject.org both work fine. We can't do this for
release-monitoring tho as we use letsencrypt certs and don't have a
wildcard. We could expand out letsencrypt role to get altnames, but just
making these seperate sites should fix it.

Signed-off-by: Kevin Fenzi <kevin@scrye.com>

playbooks/include/proxies-reverseproxy.yml

@@ -719,6 +719,16 @@
     targettype: openshift
     keephost: true
     tags: release-montoring.org
+    when: env == "production"
+
+  - role: httpd/reverseproxy
+    website: stg.release-monitoring.org
+    destname: stg.release-monitoring
+    balancer_name: app-os
+    targettype: openshift
+    keephost: true
+    tags: release-montoring.org
+    when: env == "staging"
 
   - role: httpd/reverseproxy
     website: whatcanidoforfedora.org

playbooks/include/proxies-websites.yml

@@ -883,9 +883,17 @@
     site_name: release-monitoring.org
     sslonly: true
     certbot: true
-    server_aliases: [stg.release-monitoring.org]
     tags:
     - release-monitoring.org
+    when: env == "production"
+
+  - role: httpd/website
+    site_name: stg.release-monitoring.org
+    sslonly: true
+    certbot: true
+    tags:
+    - release-monitoring.org
+    when: env == "staging"
 
   - role: httpd/website
     site_name: lists.pagure.io