Related Problem
Currently, when configuring the Sqlite notification adapter, the database file path (db/listings.db) is hardcoded. This makes it difficult for users who want to store the database in a custom location (e.g., shared drive, external folder, or cloud-synced directory) or make different jobs to write to different files.
Proposed Feature
I would like Fredy to provide a file path chooser in the UI for the Sqlite database. This would allow users to select or specify where the listings.db file should be stored instead of being limited to the default location.
Alternatives Considered
Instead of this, I also considered:
- Manually modifying the source code to change the database path.
- Using symbolic links to redirect db/listings.db to a custom location
Benefits
This would save users time by:
- Making configuration more flexible.
- Allowing advanced users to store the database where it best fits their workflow.
- Reducing the need for manual code changes or filesystem hacks.
Additional Context
