I keep all my Cantabile songs, setlists, racks and config files in version control, so I can do controlled syncing between machines, and roll back easily when I need to. On the whole this works really well…but there’s a constant annoyance, which is that settings.json contains not only settings I’ve specified, but also transient things such as the recent songs, last song, last update check etc. Consequently such files change as soon as I run Cantabile, which complicates version management. It also worries me when I want to roll back a change I made, but there are a load of other changes in there that I didn’t make.
I used to just sync my Cantabile setups between machines via Dropbox, but sometimes got clashes caused by changes in settings.json, so this isn’t specific to version control, but possibly applies to anyone sharing configurations between machines.
I was wondering how feasible it would be to keep that transient stuff in a separate file, which just holds that kind of state that’s separate from user-specified settings?
Guessing the code changes would be impractical, weighed against the benefits…I’m aware that this is probably a very niche request, and I’m may be the only Cantabile user is affected by this…