SummaryCurrently, the project uses SQLite as its backend database. While this works well for single-device usage, it becomes problematic when using the same project space across multiple devices.
Syncing the SQLite database file via tools such as SyncThing can easily lead to database corruption if the file is accessed concurrently from more than one device.
ProposalAdd support for external database backends such as MySQL/MariaDB and PostgreSQL. This would allow multiple devices to safely connect to the same central database server instead of syncing a local SQLite file.
Motivation
- Enables safe multi-device usage
- Prevents SQLite corruption due to concurrent file syncing
- Supports more advanced setups
- Improves scalability for future growth### Considerations- Database migrations strategy (when/how to run them)- Backward compatibility with SQLite- Configuration management (connection strings, credentials)- Optional: Docker-based database setups for easier onboardingI understand this may be a lower priority feature, but it would significantly improve multi-device workflows.
Plz thx bye ♥️
SummaryCurrently, the project uses SQLite as its backend database. While this works well for single-device usage, it becomes problematic when using the same project space across multiple devices.
Syncing the SQLite database file via tools such as SyncThing can easily lead to database corruption if the file is accessed concurrently from more than one device.
ProposalAdd support for external database backends such as MySQL/MariaDB and PostgreSQL. This would allow multiple devices to safely connect to the same central database server instead of syncing a local SQLite file.
Motivation
Plz thx bye♥️