Closed Bug 1224711 Opened 10 years ago Closed 10 years ago

Add custom domain DNS settings for platform-status.mozilla.org

Categories

(Infrastructure & Operations :: SSL Certificates, task)

Product:
Infrastructure & Operations
Component:
SSL Certificates
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: Harald, Assigned: rwatson)

References

Details

(Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/2159] )

https://mozilla.github.io/platatus/ needs to have a custom domain for announcement on Monday. platform-status.mozilla.org should be configured according to https://help.github.com/articles/tips-for-configuring-an-a-record-with-your-dns-provider/ to map to Github's Pages server.
This is currently proposed as part of a blog post planned for Monday, Nov 16; making it urgent.
Jeff, This needs opsec sign off as it deals with externally hosting a mozilla.org subdomain. Thanks!
Flags: needinfo?(jbryner)
This also need HTTPS enabled (requirement for Service Workers), so the DNS solution might not even work here if I am not mistaken. Does DevOps have any proxy solution that we can utilize here (similar to the use case I used cloudflare in the past for smaller projects that just needed HTTPS)?
If it's just a small project and you need SSL, probably heroku is your best bet.
Flags: needinfo?(jbryner)
Can you give me some additional information on what this page will actually be using Service Workers for? On first glance, it simply looks to be a static webpage that contains a limited subset of caniuse.com (plus the under consideration bit, which is great!), but perhaps there is more to it than what I'm missing? If it's intended to give developers a good idea of support for features, it almost seems like it would fit better under the MDN umbrella, like as platform-status.developers.mozilla.org.
(In reply to April King from comment #5) > Can you give me some additional information on what this page will actually > be using Service Workers for? So far, we're using the service worker to cache assets and API responses. Later, we'll probably offer users the chance to get push notifications about changing status of various API's. > > On first glance, it simply looks to be a static webpage that contains a > limited subset of caniuse.com (plus the under consideration bit, which is > great!), but perhaps there is more to it than what I'm missing? I think of it as our answer to chromestatus.com and www.webkit.org/status.html and dev.windows.com/en-us/microsoft-edge/platform/status/ It's something the platform team has long wanted to make.
The app is now hosted on https://platatus.herokuapp.com/ - what are the next steps for setting up the mozilla domain?
Flags: needinfo?(smani)
Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/2159]
This should be out before Thanksgiving. Could we have this by tomorrow to start QA on the final domain?
Assignee: server-ops-webops → rwatson
we are currently in a change freeze this week. I'm going to escalate this to management to try and push this through.
I'm fine with any of these three options from an opsec perspective: https://platform-status.firefox.com/ <-- I'd ideally like to move Firefox-specific services to their own domain from a security perspective, unless someone specifically wants mozilla.org. If there is a feeling that this isn't necessarily Firefox-specific, then either of these is fine: https://platform-status.developers.mozilla.org/ (more accurately represents the audience for the data) https://platform-status.mozilla.org/ R+
Flags: needinfo?(smani)
* Purchased SSL cert * added SSL via CLI: rebuilding plugins cache... done Resolving trust chain... done Adding SSL Endpoint to platatus... done platatus now served by yamanashi-7575.herokussl.com Certificate details: Common Name(s): platform-status.mozilla.org Expires At: 2017-11-27 12:00 UTC Issuer: /C=US/O=DigiCert Inc/CN=DigiCert SHA2 Secure Server CA Starts At: 2015-11-23 00:00 UTC Subject: /C=US/ST=California/L=Mountain View/O=Mozilla Corporation/CN=platform-status.mozilla.org SSL certificate is verified by a root authority. * platform-status.mozilla.org CNAME yamanashi-7575.herokussl.com updated in inventory.
Change Request: --- → emergency
Looks like everything applied and we are done here.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Thank you April, I'll bring it up with PR. Is there anything else on firefox.com, so platatus doesn't look so lost as only subdomain?
Yes, Accounts, Firefox API, OAuth, Hello, Marketplace, and Profile are all on firefox.com. We're doing the same thing with firefoxos.com, starting with updates.firefoxos.com.
April, all of those except Marketplace are services and not sites that a user would use by entering a URL or find in Google. platform-status has to be easily discovered by developers to have an impact. I leave it to PR to decide which domain is best and will also bring up the security recommendation to use firefox.com.
Well, Google will find it regardless of which domain it is on, as of how PageRank works. As I said, any of the three are fine with me, but if you feel like it's a developer-oriented documentation site, then it seems (to me) like it would best fit under MDN (.developer.mozilla.org), which is similar material. It was a bit difficult to tell from the description whether it was a website or a service, kind of sounds like a mixture of both in this case. In any case, it looks like platform-status.mozilla.org already exists, so I think it's a moot point anyways. :)
(In reply to April King from comment #16) > As I said, any of the three are fine with me, but if you feel like it's a > developer-oriented documentation site, then it seems (to me) like it would > best fit under MDN (.developer.mozilla.org), which is similar material. It > was a bit difficult to tell from the description whether it was a website or > a service, kind of sounds like a mixture of both in this case. platform-status.developer.mozilla.org feels too long to me, from an IA/ergonomics perspective; but if you did want to put this under developer.mozilla.org, then status.developer.mozilla.org seems reasonable (still long, but not *too* long) while remaining reasonably accurate (it's the *status* that a *developer* would want to know about!). Then again, there's always platform-stat.us ;-).
You need to log in before you can comment on or make changes to this bug.