Consider SQLite or similar for storing configuration and state
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.2k
- Forks
- 300
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 184
Description
Currently we store configuration and application state into files on disk using JSON. We have had various issues arising from locking, and inconsistent logic for applying updates to these files. Any change in file format has to happen in an ad-hoc manner.
Consider using something like SQLite instead. We could also consider some kind of file-based key value store instead.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not name files, tests, or an entry point. Start by locating the JSON configuration and application-state storage, then inspect the locking and update paths described in the issue. The scope and acceptance criteria remain undecided between SQLite and a file-based key-value store.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, sqlite
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100