Make it deployable

[icook]

Problem: SCM isn't currently setup in a way that facilitates switching versions without checking out code in a git repo.

Goal: Setup a continuous deployment/integration system in which multiple branches can easily be deployed to a readonly staging enviroment on the server. This could possibly be setup to occur automatically on new branch creation/push etc.

Right now the simplecoin package isn't setup in a way that it can be "bundled" per se. The main blockers that I know of are news.yaml, and alerts.yaml, which use hardcoded paths. This is a trivial fix.

Another slightly more complex issue is setup.py not bundling templates and static when it installs in a virtualenv. IE, static and templates will load improperly if not installed with pip install -e ., since pip install . will not copy the templates, etc.'

I'm not sure however that bundling static and templates is actually the right choice however, since I think it might be a useful way to allow customized templates or static assets to be used via configuration. Customizing the template path is again simple (config values), but I'm not sure quite how we'd go about customizing the static path since that's actually configured in nginx, not scm.

[ericecook]

I think this is definitely a good thing to get squared away. One of the big things our software is lacking is ease of setup compared to others like NOMP and MPOS, so this is a logical step.

If we make the templates/static content more generic (like discussed in #151) I think that'd be fine to bundle.

As for the static path being configured in the webserver - I'm not sure the best way to handle that. Ideally we want it to be something the user doesn't have to touch, so either handle the routing in SCM - or auto-configure a webserver? Both options seem kinda shitty.