Migrating Tinderbox Data
If you need to migrate Tinderbox to a new fork or are re-downloading your repo and want to save your facial models, follow these steps to prevent data loss.
Note: data migration isn't possible in all cases. This is because data is stored using MapDB, a simple disk-persisted key/value database that is integrated with Tinderbox.
Data migration will not after an upgrade when java classes or models have been removed from the repository and are no longer available in the classpath. For example, if you pull a new change for Tinderbox where a commit removes a file such as FacialModelData.scala that is stored within MapDB, then the application will fail to start after upgrade. The only fix is to delete data models and start from scratch. This is because MapDB attempts to find the class via the Java Class Loader, and throws a fatal error when it can no longer find the class.
To see a similar problem where this applies, check out this issue: https://github.com/crockpotveggies/tinderbox/issues/23
To move your accumulated data, copy the contents of the data folder and place a safe copy that is located elsewhere on your computer. If you are re-downloading the Tinderbox repository, you can then re-paste the data folder back in the same location (which is the root of the repository). Note the caveats above, where this will not always work.
Copying the data folder to safe location can also be used for backing up models, if you wish to do so.