710597 - Setup www.itisatrap.org

Status: RESOLVED FIXED

(www.mozilla.org :: General, defect)

Description

[Anthony Ricaud (:rik)]

+++ This bug was initially created as a clone of Bug #681945 +++

Git repo is at https://github.com/mozilla/itisatrap.
This is a static website.

Let me know if you need more information.

Comment 1

[Jake Maul [:jakem]]

Should also fix stage (itisatrap.allizom.org) while we're at it, since it'll be basically the same process.

Should also set dev (itisatrap-dev.allizom.org) to auto-update. It currently does not.

Comment 2

[Anthony Ricaud (:rik)]

Any update on this?

Comment 3

[mcbmoz]

Hey Jake, friendly ping on this for a status update (I know you guys have a ton going on), it's a blocker for Bug 662213 and that team is asking for an update there, and this will help us help them.

Comment 4

[Jake Maul [:jakem]]

Old bug update:

The dev site is being auto-updated: http://itisatrap-dev.allizom.org/

The stage site is fixed and should be functional: http://itisatrap.allizom.org/

Let me know if any changes are needed to these, or if you need a code push for stage (it is current as of this comment).

As for the prod site... are we still good with "www.itisatrap.org"? It looks like we own that domain, but it's not set up in DNS. I can do that pretty quickly if that is still the plan.


Also, do we need SSL for the prod site? If so, we'll need to buy a cert. I'm not sure under what conditions users are likely to land on this site, and if they'll be coming in over SSL or not, or if we'd want them to get an EV cert (more expensive).

Comment 5

[Jake Maul [:jakem]]

The prod site is alive now, too: http://www.itisatrap.org/

Note that SSL will return the wrong cert... it's just on our generic shared IP that uses SNI to choose a cert, but since there isn't one, it'll be wrong. We can replace with a proper cert, or move to an IP that doesn't support HTTPS. Not an IT decision. :)

Comment 6

[Gian-Carlo Pascutto [:gcp]]

Is there any reason this can't be closed?

Comment 7

[Jake Maul [:jakem]]

Since no decision was ever reached (or at least, communicated to IT) about purchasing an SSL certificate for this, I have moved this to a non-SSL IP, per comment 5. This should prevent future complaints about this site supporting SSL but having an invalid certificate. If we do need SSL support, I recommend filing a new bug for it.

That's all that was outstanding here. Closing.