This backend works just like the X11 backend, except it starts HamClock
on its own rather than relying on an existing instance. As the name
implies, it is intended for SaaS environments where multiple HamClocks
may be running on a single machine, and running unused instances would
be a significant waste of resources.
* Add support for config file
Closes#1
* Support changing config path
The path to the config file is accepted as an argument
* Remove old code
Remove the code for the old backend selection method
This commit converts the server to use Tornado. Unfortunately, I had to
convert part of the code to async, but I avoided it as much as possible.
Closes#7
