Currently, persistence is implemented with a JSON manifest (as our source of truth) that references files saved in a persistence directory. This has the properties of:
hard to edit manually (in case of video file corruption)
hard to remove unneeded files programmatically
doesn't sync to the files that are actually there (meaning there are "ghost" files that aren't tracked by the manifest but exist nonetheless)
The ideal solution is outlined in the "Renovate Persistence" milestone. In the meantime, let's start by making the manifest responsive to what's actually there
Currently, persistence is implemented with a JSON manifest (as our source of truth) that references files saved in a persistence directory. This has the properties of:
The ideal solution is outlined in the "Renovate Persistence" milestone. In the meantime, let's start by making the manifest responsive to what's actually there