Closed escattone closed 5 years ago
wiki.developer.allizom.org
and wiki.developer.mozilla.org
to point to their respective ELB's (bypassing their respective CDN's)wiki.developer.mozilla.org
and beta.developer.mozilla.org
to the prod CDN's list of alternate domain names (CNAME
's)/api/v1/doc/*
from S3/api/v1/whoami/*
from the ELBI published all of the production documents to the production S3 bucket. Well, all except one. There is this one evil document (/zh-CN/docs/Archive/Web/LiveConnect
) which crashes the celery worker when it is run. When I tried to publish it manually it crashed Python as well. Also, when I request the document like https://developer.mozilla.org/zh-CN/docs/Archive/Web/LiveConnect, I wait and wait and wait (>30 seconds) but no response. Something is rotten with that document.
Given that it's under /Archive, it's probably not a big deal to delete that document. It would be great to figure out what's wrong with it, but not if it turns into a rabbit hole.
I also re-published all of the stage documents to the stage S3 bucket. I did this because https://github.com/mozilla/kuma/pull/5402 added an enSlug
attribute to the JSON that the document API returns.
I'm going to document the results of my testing against prod.
Load https://developer.mozilla.org/en-US and https://wiki.developer.mozilla.org/en-US
Load https://beta.developer.mozilla.org/en-US
Load https://developer.mozilla.org/en-US/docs/Web/HTML, https://wiki.developer.mozilla.org/en-US/docs/Web/HTML, and https://beta.developer.mozilla.org/en-US/docs/Web/HTML
The Firefox and Chrome functional tests as well as the headless tests pass when run against stage (https://developer.allizom.org) from Jenkins.
The Firefox and Chrome functional tests as well as the headless tests pass when run against https://wiki.developer.mozilla.org.
Submitted https://github.com/mozilla/kuma/pull/5426 (minor tweaks) to address a testing issue with the headless tests when run against the production or wiki
domains.
The Firefox and Chrome functional tests as well as the headless tests pass when run against https://developer.mozilla.org.
These URLs should have similar results for anonymous or logged-in users:
Test these URLs as an anonymous user:
Some things to try with a regular account, to exercise write functionality:
{{cssxref("background")}}
.Some things to try with an admin account, to exercise restricted functionality:
Test anomalies (none are failures in regard to this effort, but indicate follow-on work):
beta
archive pages are missing the striped warning border. This is something we need to address in the front-end for the beta
domain archive pages.mdnwebdocs-bot
had its toc_depth
attribute modified from its original value of 4
to 0
, effectively reducing the $toc
response to an empty one. I'm worried now that this has happened to all revisions modified by the mdnwebdocs-bot
.The acceptance criteria has been met.
User story
As a developer, I want to prepare production to handle the separate
beta.developer.mozilla.org
andwiki.developer.mozilla.org
domains so we're ready when we make those domains public.Acceptance criteria
developer.mozilla..org
,beta.developer.mozilla.org
, andwiki.developer.mozilla.org
.Tasks
/api/v1/doc/*
/api/v1/whoami/*
beta.developer.mozilla.org
andwiki.developer.mozilla.org
(pointing to the prod CDN and the prod ELB respectively)beta.developer.allizom.org
andwiki.developer.allizom.org
(pointing to the stage CDN and the stage ELB respectively)developer.mozilla..org
,beta.developer.mozilla.org
, andwiki.developer.mozilla.org
(this task depends on the prior successful completion of https://github.com/mdn/sprints/issues/1205 -- the details are here)