Apologies for the long topic, just trying to make sure I explain myself thoroughly. Thanks for reading!
Feature request
Can joplin add a feature to simultaneously(or serial) sync to multiple locations?
It seems to me that joplin is able to support multiple sync targets, just not simultaneously. One can switch back and forth between targets, it will sync fine. Can we make this always happen rather than needing to switch back and forth?
Details
I understand this looks like a workaround but if there was support for multiple sync targets I would be able to version, encrypt, and offsite my backup, in a joplin native way while still being able to sync my notes with my phone.
Setup:
- Setup encryption configuration
- Sync to cloud provider for mobile sync
- Sync to file system to a git managed directory. This way I get encrypted versioned backups as opposed to raw export
- Use fswatch or cron to trigger git add, commit, push for rollback. While files may not be totally atomic, in a disaster I should be able to recover the majority of my notes since they’ll eventually fsync to the filesystem and the disaster would have to happen during a sync. If a half write was committed, I can just keep rolling back until the files make sense. The versioning can also protect against silent corruption
Reasoning:
Even evernote has had a history of data loss and a backup strategy is key for any long term note strategy.
As a user of the mac gui app, I don’t have access to the cli export command, and I’d like to avoid using the cli with the --profile flag since then I have to worry about if the sqlite formats have changed between the cli and gui app because one version is out of date. Additionally even if I did have the cli tools, raw exports are unencrypted, and since I want offsite backups, that’s a non starter
Even if I had the export commands, and exported to jex or a raw export then ran my own encryption, I’d be only doing what joplin already knows how. I want to take advantage of each .md being encrypted so that each checkin only increases my repo size by the size of the new encrypted note rather than a large blob
Downsides:
The encryption code becomes even more critical path, if there’s bugs in encryption, both the backup and the cloud version will be corrupted. This is mitigated by git versioning that most likely not all your notes will be mangled, but it is a risk. Hopefully if this ever happens this would be caught while at least one plaintext version of the notes exists and then we have an escape hatch, but its not foolproof
(Sneaky alternate feature request)
Can the mac app come bundled with it’s own scheduled export command or a simple cli tool for export? That way, I could also work around creating my own backup strategy like laurent’s.