Greetings.
Last week I setup codecs.stg.fedoraproject.org for testing and I think
everything there is looking good.
I'd like to push it in production too.
This will involve:
- adding dns for codecs.fedoraproject.org (pointing to proxies).
- populating /srv/web/codecs.fedoraproject.org/ content with the current
repos/rpms.
- The below small patch and ansible run on proxies.
diff --git a/playbooks/include/proxies-fedora-web.yml b/playbooks/include/proxies-fedora-web.yml
index 27e7fe9..5f275fe 100644
--- a/playbooks/include/proxies-fedora-web.yml
+++ b/playbooks/include/proxies-fedora-web.yml
@@ -46,7 +46,6 @@
when: env == "staging"
- role: fedora-web/codecs
website: codecs.fedoraproject.org
- when: env == "staging"
# Some other static content, not strictly part of "fedora-web" goes below here
- role: fedora-docs/proxy
diff --git a/playbooks/include/proxies-websites.yml b/playbooks/include/proxies-websites.yml
index b681ea1..a1812a8 100644
--- a/playbooks/include/proxies-websites.yml
+++ b/playbooks/include/proxies-websites.yml
@@ -581,7 +581,6 @@
server_aliases: [codecs.stg.fedoraproject.org]
sslonly: true
cert_name: "{{wildcard_cert_name}}"
- when: env == "staging"
- role: httpd/website
name: beaker.qa.fedoraproject.org
There's no deadline I know of here, but it would be nice IMHO to get
this all in place and ready for the fedora-repos changes and mark it
off our lists.
+1s?
kevin
Attachment:
pgp2LWH0fxeB0.pgp
Description: OpenPGP digital signature
_______________________________________________ infrastructure mailing list infrastructure@xxxxxxxxxxxxxxxxxxxxxxx http://lists.fedoraproject.org/admin/lists/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
