Config & migrations

## Management
Both Jia and the scheduler have management scripts. Jia's is `./manage.py` and the scheduler's is `./scheduler.py`.

Running the Jia server:
`./manage.py -c settings.cfg runserver`

Running the scheduler:
`./scheduler.py -c settings.cfg run`

## Migrations
Now using [Flask-Migrate](https://github.com/miguelgrinberg/Flask-Migrate)

To bring an existing Jia database onto the migration system, do:
```
./manage.py -c settings.cfg db stamp 69423a89666
```
And for the scheduler:
```
./scheduler.py -c settings.cfg db stamp 265ea1d587a3
```

Run migrations using:
```
./manage.py -c settings.cfg db upgrade
```

## Resolved issues
* #256 
* #246 
This will actually work just fine because we have a request context here. I could change it for consistency, but I left it because why not have as much of it as clean as possible? In the future if we move off the singleton model, it will be that much less that needs to be modified.