Make Mutalyzer easier to install, test, and run

This merge requests tracks the effort of making Mutalyzer easier to install, test, and run. This includes moving away from the idea that our local development environments should be identical to the production server. For development, it should be very easy to run Mutalyzer without setting up init scripts or Apache for that matter.

Along the way I'm doing some general cleanup, make the code more consistent (e.g., in variable naming) and update docstrings.

Completed

• Fixes for installing/running Mutalyzer from a virtual environment. (!4 (merged))
• Switch from TAL to Jinja2. (!3 (merged))
• Refactor user interfaces. (!5 (merged))
• Move from configobj to Python module based config. (!7 (merged))
• Use SQLAlchemy as ORM. (!8 (merged))
• Use Redis for stat counters. (!10 (merged))
• Port website from web.py to Flask. (!11 (merged))
• Isolated unit tests (fixtures, cache). (!12 (merged))
• Merge administrative tools into one interface. (!13 (merged))
• Display announcement on website. (!14 (merged))
• Database migrations with Alembic. (!15 (merged))
• Update documentation and use Sphinx. (!16 (merged))
• Move to semantic versioning. (!22 (merged))

(Please consult the linked merge requests for compiling migration notes.)

In progress

• Automated deployment with Ansible. (mutalyzer-deployment)

Links

• Setting up Django with Nginx, Gunicorn, virtualenv, supervisor and PostgreSQL
• Basic Alembic Migrations with Flask
• Database Migrations with Alembic, SQLAlchemy and Flask
• factory_boy

mentioned in issue #1 (closed)

mentioned in issue #3 (closed)