Add a way to rebuild recording DB from on-disk data.
Open
@defnull is already working on this.
Since Mar 21, 2026.
- Dominant language
- Python
- Stars
- 6
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
In case of a disaster (lost DB, no backups) or after a hard crash, it would be nice to have a cli command to scan on-disc recordings and make sure the db state matches the on-disk state.
Most of the db state can be recovered from the original metadata.xml files in the storage directory. The tenant name is part of the storage path and also known. The current publish/unpublish state can be derived from the presence of symlinks in the playback directory. Changed metadata is not stored on disk, though. An additional json file in the storage directory would solve this issue and allow complete recovery from a lost database.
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.
Assessment
This issue has not been assessed yet.