feat: add sqlite backend for storage #483
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR aims to add a SQLite backend for server storage. It is provided as a replacement of
jsonDB
andbboltDB
. This new storage is currently registered as the default backend.gorm
(https://gorm.io/) is used as an ORM, allowing to abstract models and underlying database storage (MySQL, PostgreSQL, SQLite, SQLite server). Only SQLite is implemented in this PR.A new parameter has also been added to server CLI,
-b
to continue using "legacy" storage backends.Advantages of this new storage backend:
Settings are still stored in JSON format, easing the pre-configuration of the server.
This PR is needed for #421 to cache downloaded informations about films and series using TMDB api. This will prevent reaching quota by caching informations, without impact on memory consumption.
Needed steps before PR being ready:
Let me know if there is something I can do to improve this PR !