Automated builds based on travis

Love the idea and project. I was wondering if it makes sense to move the build/deploy process to travis instead? I do the same at [hackercouch](https://github.com/hackercouch/hackercouch/blob/master/_script/deploy.sh) and it currently runs the deploy on every commit to master.

In order to keep it updated, we also use nightli.es as a backup. Thinking if would be possible to pipe the github event for issues.\* on the repo to trigger a build in travis.

The issue discusses Travis, GitHub issue events, nightli.es, and the example _script/deploy.sh from hackercouch. Start by comparing that deploy script with this repository's current build and deployment setup. Done requires a concrete, agreed design for builds on commits to master, issue-event handling, and the nightli.es backup.

Written by the indexing model from the issue text.