Sqlite (#75)

* file structure

* auto-test

* take 2

* refactor ap scheduler and startup process

* fixed scraper error

* database abstraction

* database abstraction

* port recipes over to new schema

* meal migration

* start settings migration

* finale mongo port

* backup improvements

* migration imports to new DB structure

* unused import cleanup

* docs strings

* settings and theme import logic

* cleanup

* fixed tinydb error

* requirements

* fuzzy search

* remove scratch file

* sqlalchemy models

* improved search ui

* recipe models almost done

* sql modal population

* del scratch

* rewrite database model mixins

* mostly grabage

* recipe updates

* working sqllite

* remove old files and reorganize

* final cleanup

Co-authored-by: Hayden <hay-kot@pm.me>

docs/docs/changelog.md

@@ -1,7 +1,32 @@
 # Release Notes
 
+## v0.1.0 - Initial Beta
+### Bug Fixes
+  - Fixed Can't delete recipe after changing name - Closes Issue #67
+  - Fixed No image when added by URL, and can;t add an image - Closes Issue #66
+  - Fixed Images saved with no way to delete when add recipe via URL fails - Closes Issue #43
+
+### Features
+  - Additional database! sqlite is now supported! Closes #48
+  - All site data is now backed up.
+
+
+### Code Improvements
+  - Unified Database Access Layers
+  - Poetry / pyproject.toml support
+  - Local development without database is now possible!
+  - Major code refactoring to support new database layer
+  - Global variable refactor
+
+### Break Changes
+
+!!! warning
+    As I've adopted the SQL database model I find that using 2 different types of databases will inevitably hinder development. As such after release v0.1.0 support for mongoDB will not longer be available. Prior to upgrading to v0.2.0 you will need to export your site and import your settings after updating. This should be a painless process and require minimal intervention on the users part. Moving forward we will do our best to minimize changes that require user intervention like this. 
+
+
 ## v0.0.2 - Pre-release Second Patch
 A quality update with major props to [zackbcom](https://github.com/zackbcom) for working hard on making the theming just that much better!
+
 ### Bug Fixes
   - Fixed empty backup failure without markdown template
   - Fixed opacity issues with marked steps - [mtoohey31](https://github.com/mtoohey31)

docs/docs/getting-started/backups-and-exports.md

@@ -3,7 +3,7 @@
 
 All recipe data can be imported and exported as necessary from the UI. Under the admin page you'll find the section for using Backups and Exports. 
 
-To create an export simple add the tag and the markdown template and click Backup Recipes and your backup will be created on the server. The backup is a standard zipfile containing all the images, json files, and rendered markdown files for each recipe. Markdown files are rendered from jinja2 templates. Adding your own markdown file into the templates folder will automatically show up as an option to select when creating a backup. To view the availible variables, open a recipe in the json editor.
+To create an export simple add the tag and the markdown template and click Backup Recipes and your backup will be created on the server. The backup is a standard zipfile containing all the images, json files, and rendered markdown files for each recipe. Markdown files are rendered from jinja2 templates. Adding your own markdown file into the templates folder will automatically show up as an option to select when creating a backup. To view the available variables, open a recipe in the json editor.
 
 To import a backup it must be in your backups folder. If it is in the backup folder it will automatically show up as an source to restore from. Selected the desired backup and import the backup file.