Issues/417

This branch is not really intended for merging into the develop branch. Instead, this branch includes changes that allow the authoring tool to be easily deployed as an heroku app. 

The main roadblock for this is the ability to run `grunt` on an heroku node to build the frontend for the app. It may be possible to use `grunt` by using a grunt focused buildpack (https://github.com/mbuchetics/heroku-buildpack-nodejs-grunt), I felt that this might be introducing a dependency we should try to do without. This branch works around the issue by including the frontend/build directory in the git repository.

I'd like to discuss and perhaps change some of the decisions we made earlier on about our dependency on `grunt`, as well as assumptions about how we want to deploy the authoring tool.

To deploy this as an heroku app:

````
$ heroku create
$ git push heroku issues/417:master
````

I used the mongohq add on:

````
$ heroku addons:add mongohq:sandbox
````

Visit your app via the url and take note of the following details during the install process:

 - on the "Configure Server" page, the hostname should be the hostname of the heroku app, and the port for an heroku app should be "80". When installing the tool locally, the hostname will usually be localhost, and whichever port the app is listening on.
 - on the "Configure Database" page, be sure to set the host, port, username and password correctly for your mongo server. MongoHQ provides the full uri in the format `mongodb://<user>:<password>@<database host>:<port>/<database name>`
 - on the "Configure Default Tenant" page, the name for the master tenant should be set the name of the database provided by your mongodb addon - that's the name after the final '/' in the MongoHQ uri.