cleodora-forecasting / cleodora-forecasting/cleodora
[Idea] Store the application version in the DB and don't allow starting cleosrv if the DB is too new
Open
- Dominant language
- Go
- Stars
- 24
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
The idea being that users are prevented from opening the DB with an old binary by mistake.
Maybe provide a --force parameter to override this in case of bugs.
Contributor guide
Research direction
No files or tests are named. Start by locating the cleosrv startup path, database schema/version handling, and existing command-line flag definitions. The work is complete when the database records the application version, newer databases are rejected by older binaries, and a documented --force override is covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100