MozFest 2014 Site: Prepare emergency response plan in case site blows up

RESOLVED FIXED

Status

Mozilla Foundation Communications
Website
RESOLVED FIXED
4 years ago
4 years ago

People

(Reporter: Erika Drushka, Assigned: Erika Drushka)

Tracking

Details

(Whiteboard: [studio mofo][mozfest])

(Assignee)

Description

4 years ago
In the spirit of "Better Safe Than Sorry" let's make sure we have a plan in case the site goes down during the festival.
(Assignee)

Comment 1

4 years ago
JP will create a static copy of the site we can fall back on if necessary.

Comment 2

4 years ago
Already all done!  I've got DNS set so it is a 20 second change with a 60 second wait to failover.

2014.mozillafestival.org.s3-website-us-east-1.amazonaws.com
(Assignee)

Comment 3

4 years ago
If the schedule app explodes, here's the link to the schedule Google doc: http://bitly.com/MozfestSchedule  [Case sensitive]

Process to use this spreadsheet:
1. Make a back-up copy of the spreadsheet and add link to this bug
2. On the original spreadsheet, remove the column which displays email addresses
3. Change the settings to make it viewable by anyone, but only editable by people with Mozilla addresses

We can print posters with a QR code and the Bitly link and post around the building. This would only be necessary if the app goes down for a significant period of time.
(Assignee)

Comment 4

4 years ago
Nothing blew up. Good job, team!
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED

Comment 5

4 years ago
Due to incredible amounts of wisdom our team had this year, we've got it setup so that we make this years into static html (using the same backup process we used here) and this year, we'll not lose any links!  We named the canonical url 2014.mozillafestival.org.  Thus, when we're ready next year for 2015.mozillafestival.org, there's only one Wordpress install for that, and the rest is inexpensive/safe static dating back to 2011.mozillafestival.org
You need to log in before you can comment on or make changes to this bug.