Make a start on auth models
Setup boilerplate for login and sessions

This is just a starting point really, there is lots of room for improvement still, for example using redis for session later, etc.

The secret key isn't exactly kept secret for now so it's just a default setting stored in GIT in the .ini files. The CMS is nowhere near production ready anyway, so this is OK for the time being, but later we'll need a way to be able set the secret key, but not store it on GIT.
Lots more work on auth, can actually log in and out now

* A base layout class for things we'll need in every view (settings, session, and request object for example)
* Added model managers class (similar to Django) to every model, though there is still a refactoring opportunity here to get rid of repetitive code
* Added a few methods to each model: save() and delete(), these could also be refactored into a common base class
* Refactor views.py into a module which allows for expansion
* Added auth views (login, logout view)
* Added login.jinja2 template