Refactored ORM to use peewee instead of SQLAlchemy

[jjohnson338]

This is my swing at #2

I've refactored SQLAlchemy out and am using an ORM called peewee. I've added pre and post hooks for web requests to both open and close the db. I'm not able to replicate (or am not sure how to replicate) the issue mentioned in #2 . @cmeury If you get a chance, could you test this PR out and see if it solves the issue for you? Or point me in a direction to reproduce the issue on my local.

[cmeury]

Hey @jjohnson338 -- awesome! I can test it, but currently there are conflicts.

[jjohnson338]

If the refactor works for you, I don't mind correcting the merge conflicts, but don't want to spend the effort if it might get dropped. But do let me know if this solves your issue.

[cmeury]

@jjohnson338 Dude, I had a moment, lol. Of course I can test it in the branch, no need to fix the conflict before-hand. Will let you know :)

[cmeury]

My Synology server got an automatic update and messed up my configuration; doesn't look like I'll be able to test this in the near future. :/ Let's keep it around until I get around to fix things.

[jjohnson338]

Sure thing. If it works out, should be a trivial merge. peewee and SQLAlchemy have mostly identical query syntax and nearly identical model definitions. If I continue updates to queries and such, I'll stick with main branch using SQLAlchemy for now