I appreciate the "no delete" starting point, but is there a way to override that if desired? I can see the workaround is to delete one side and sync so no big deal just curious
Currently, 'dsync diff' will show (conflict) files including any that does not exist on either side (local or remote) and requires user to those cases manually. If you rm a file locally and push, Drive keeps it, and the next pull brings it back. To remove something, delete it on both sides yourself (locally plus on the Google Drive).
But this is a fair ask, I'd keep the default behaviour of 'no delete' but I'll work on to add a --delete flag for users to override that (in the release v0.4.0 this week). Thanks for the feedback.
This is faster (on tracking changes via diff, handling resumes & parallel streams) and narrow in scope than rclone. rclone is a fantastic tool for those you're used to it, there is no reason to pick this over rclone if one is happy with it.
Not able to develop and test it on Windows and I hit some blocker on arm64 cross compiling so I've skipped it for now, sticking with macOS and Linux. Are you a Windows user?
I appreciate the "no delete" starting point, but is there a way to override that if desired? I can see the workaround is to delete one side and sync so no big deal just curious
Currently, 'dsync diff' will show (conflict) files including any that does not exist on either side (local or remote) and requires user to those cases manually. If you rm a file locally and push, Drive keeps it, and the next pull brings it back. To remove something, delete it on both sides yourself (locally plus on the Google Drive).
But this is a fair ask, I'd keep the default behaviour of 'no delete' but I'll work on to add a --delete flag for users to override that (in the release v0.4.0 this week). Thanks for the feedback.
Update: a --delete option has been added, when specified on Drive, macOS & Windows it moves files to trash, on Linux it will permanently delete files.
This is really interesting. I appreciate the ability to resume an upload.
Thank you.
What's different between this and rclone?
This is faster (on tracking changes via diff, handling resumes & parallel streams) and narrow in scope than rclone. rclone is a fantastic tool for those you're used to it, there is no reason to pick this over rclone if one is happy with it.
I've explained a bit more here: https://www.reddit.com/r/macapps/comments/1wahrfw/comment/p8...
> Windows is not supported.
Any particular reason?
Not able to develop and test it on Windows and I hit some blocker on arm64 cross compiling so I've skipped it for now, sticking with macOS and Linux. Are you a Windows user?
i'm on windows feel free to send me a ticket on your app and I can help out. i'm also pretty good with GCP oauth apps.
http://github.com/tonymet
Thanks Tony. Windows binary of DriveSync is available on the releases now, any testing and feedback is much appreciated: https://github.com/scaleninja/drivesync/releases/tag/v0.4.1
For setup (oauth etc) I wrote this guide that you may refer https://github.com/scaleninja/drivesync/blob/main/docs/SETUP...
I’m a big fan of “use your own storage” apps like this great work!
Thanks!
[flagged]
[dead]