Setup github pages hosting and update README to reflect change

.gitignore

@@ -1,3 +1,4 @@
 /node_modules
 *~
 /html/data
+/gh-pages

README.md

@@ -1,7 +1,7 @@
 ## Realtime Service Status for Mozilla Persona
 
 This repository holds the status reporting system for Mozilla Persona
-to be hosted at http://personastatus.org.  People who care about 
+to be hosted at http://status.persona.org.  People who care about
 Persona can check the status of the service at that url.  People working
 on persona can report incidents by adding files to this repository.
 
@@ -21,7 +21,7 @@ file is plain text prose.  For example:
 
     We've isolated the problem, it's a bogus flux capacitor.  We're going to try to stop
     in the Aquila System to buy one from the semi-hostile Midorians there.
-    
+
 **NOTE:** Date parsing is pretty flexible.  When an event occurs, type `date` at your terminal,
 and then embed this in your report.
 
@@ -36,31 +36,31 @@ and `resolution(.txt)?`.
 2. write a `discovery.txt` file
 3. commit it
 4. push it up to github
-5. push updates to the personastatus awsbox (must be a core dev with a key in https://github.com/mozilla/identity-pubkeys)
+5. build and publish the update to gh-pages
 
-        git remote add personastatus.org [email protected]:git
-        git push personastatus.org master
+        scripts/build-gh-pages.sh
+        scripts/publish-gh-pages.sh
 
 ## How you resolve an incident
 
 1. write a `resolution.txt` file in the directory
 2. commit it
 3. push it up to github
-4. push updates to the personastatus awsbox (must be a core dev with a key in https://github.com/mozilla/identity-pubkeys)
+5. build and publish the update to gh-pages
 
-        git remote add personastatus.org [email protected]:git
-        git push personastatus.org master
+        scripts/build-gh-pages.sh
+        scripts/publish-gh-pages.sh
 
 ## Some details
 
 Scripts in `scripts/` are responsible for validating the pile of files in `events/`,
-turning them into JSON that the webpage (under `html/` can render) 
+turning them into JSON that the webpage (under `html/` can render)
 
 ## hacking on it
 
 1. clone it
 2. npm install
-3. mkdir html/data 
+3. mkdir html/data
 4. scripts/to_json.js > html/data/1.json
 5. scripts/run.js
 6. open http://127.0.0.1:8080/

html/CNAME

@@ -0,0 +1 @@
+status.persona.org

scripts/build-gh-pages.sh

@@ -0,0 +1,25 @@
+#!/bin/bash
+
+set -e
+
+cd "$(dirname "$0")/.."
+
+if [ -z "$GH_TOKEN" ]; then
+    GH_URL="${GH_REF:-$(git config --get remote.origin.url)}"
+else
+    GH_URL="${GH_TOKEN}@${GH_REF}"
+fi
+
+! test -e gh-pages || rm -rf gh-pages
+git clone "$GH_URL" gh-pages --reference . --branch gh-pages --no-checkout
+npm install
+scripts/to_json.js
+cp -a html/* gh-pages/
+cp .git/config gh-pages/.git/config
+
+cd gh-pages
+
+git config user.email '[email protected]'
+git config user.name 'Travis Build'
+git add --all .
+git commit -m 'Github Pages Build'

scripts/publish-gh-pages.sh

@@ -0,0 +1,5 @@
+#!/bin/bash
+
+set -e
+cd "$(dirname "$0")/../gh-pages"
+git push origin gh-pages:gh-pages