Is your feature request related to a problem? Please describe.
slow performance for user logins/activity viewing and sqlite locking on larger environments
see #1470
Additionally, the events.db file seems to grow quite large very quickly. This could serve to minimize bloat on the docker host.
I have only 11 users and 10 peers. The events.db file is already nearly 1GB in size.
Describe the solution you'd like
a method to define an externally usable database server in the StoreConfig section
postgresql seems like the most viable candidate
additionally a migration tool akin to the one which moves existing data between json and sqlite options
Describe alternatives you've considered
mariadb or mysql could be possible solutions as well
Additional context
Having an external DB would also simplify backups and migrations of the base docker host.
Is your feature request related to a problem? Please describe.
slow performance for user logins/activity viewing and sqlite locking on larger environments
see #1470
Additionally, the events.db file seems to grow quite large very quickly. This could serve to minimize bloat on the docker host.
I have only 11 users and 10 peers. The events.db file is already nearly 1GB in size.
Describe the solution you'd like
a method to define an externally usable database server in the StoreConfig section
postgresql seems like the most viable candidate
additionally a migration tool akin to the one which moves existing data between json and sqlite options
Describe alternatives you've considered
mariadb or mysql could be possible solutions as well
Additional context
Having an external DB would also simplify backups and migrations of the base docker host.