Sync/backup options (two-way, one-way)
- keep exact snapshot on both sides,
- (Safety mode) keep superset on both sides, don't delete locally nor remotely; (Exact details to be agreed),
- sync from local to S3, delete on S3 if deleted locally,
- sync from S3 to local, delete locally if deleted on S3,
- backup from local to S3, don't delete on S3,
- backup from S3 to local, don't delete locally,
Conflict resolution algorithms to be spec'd out.
Postponed ETA from April to May.
This is to let you know that this feature is actively being worked on, but we need your feedback on this.
At the moment we're having a working prototype of two-way and one-way sync on desktop clients. It needs more testing (especially on multiple platforms) and handling edge cases.
We still need to handle conflicts (any preferred options? Shall we apply some automatic conflict resolution, e.g creating new file entry with e.g. "- Android conflict 2023-04-20" or perhaps allow user to review conflicting versions and decide what to do?
The other bit where we're not exactly sure is how to implement Syncing on mobile devices. Do you have an example of app/file manager were syncing works in a way that you would like to see in S3Drive?
In other words, do you have the app which allows you to open remote file (e.g. in cloud), modify it locally and then allow saving it back or does that automatically?
My use case if that helps the development:
This feature would enable me to synchronize my photos and other files from S3 to my desktop. This can reduce my storage cost and keep me using this software instead of choosing another one that can be used for synchronization on both side (mobile and desktop).
Maeve Cantrell: Thank you for your feedback. Am I right to understand that in your case one-way synchronization (that is from S3 to desktop) would be sufficient?
If you delete files on the S3, would you also like these files to be deleted locally?
We're already having a working prototype, but need more time to test it thoroughly even before releasing (beta) version.
There are also couple challenges that we face related to S3 protocol and time precision which is crucial to perform efficient syncing, but we have some workarounds which in principle could work before we come up with more robust solution.
marked this post as
marked this post as