Database...

[austinwbest]

Move settings to a db and only use files for non persistent data. There is an sqlite branch where all of this is taking place & i am force pushing to it so i do not recommend messing with it unless discussing it first.

base

• [x] Create a database class to handle/abstract the calls
• [x] Create a simple migration system

api

• [x] Implement the API for all database calls (local and remote implementation)
• [x] Make sure the API does not trigger curl calls (intended for remotes) on the local instance

global settings

• [x] Move global settings from settings.json to the database
• [x] -- Migrate existing systems
• [x] -- Rewrite the UI to use the database
• [x] -- Rewrite the crons to use the database

container settings

• [x] Move container settings from settings.json to the database
• [x] -- Migrate existing systems
• [x] -- Rewrite the UI to use the database
• [x] -- Rewrite the crons to use the database

container groups

• [x] Move container group settings from settings.json to the database
• [x] -- Migrate existing systems
• [x] -- Rewrite the UI to use the database

update settings

• [x] Move update settings from settings.json to the database
• [x] -- Migrate existing systems
• [x] -- Rewrite the UI to use the database
• [x] -- Rewrite the crons to use the database

remote servers

• [x] Move server settings from servers.json to the database
• [x] -- Migrate existing systems
• [x] -- Rewrite the UI to use the database

notifications

• [x] Move notification settings from settings.json to the database
• [x] -- Migrate existing systems
• [x] -- Rewrite the UI to use the database
• [x] -- Multiple platforms to be implemented dynamically (prepare for Telegram)
• [x] -- Rewrite the crons to use the database
• [x] -- Rewrite the crons to use the new multiple system
• [x] -- Allow for multiple uses of the same platform