New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Delete orphan files when synchronizing #12171
Comments
Milestone 2.8 deleted |
I really want this as well. It would make CyberDuck perfect for me :) |
Replying to [comment:7 dkocher]: Does this mean it's not be implemented? Cheers |
I can't believe this has been here for 10 years. It is an essential feature of synchronisation. Makes Cyberduck not fully usable for me, I'll have to look elsewhere. Sorry, no donation without this feature possible. |
I can also not believe, that this feature ist not included for this long time. It is a very important feature for synchronisation. Without this, it is only a simple upload/download... Add this, please! |
You might be better served with Mountain Duck and then use |
Yes it is an option - when there is a support for CLI so that you can use Batch Scripts... See also #9053. |
Please add this functionality to delete destination file on Windows Azure storage when the local source file is deleted. This should be a main feature of the Synchronization/Mirror feature of CyberDuck. Else, all these files that I delete are still on Azure and I have to use another file dif utility to compare directories to see what is still in the destination folder on Azure and then manually delete those files else my Azure storage continues to grow and costs me money for unnecessary storage after synchronization. |
please please please please please ... |
Yes! This is really needed! |
Yeah... Kinda needed if your looking to use this as a backup tool. Bummer... I thought this was bound to be supported when I purchased. :( |
It would be very nice if the synchronization funcionality included an option to delete orphan files from the remote directory.
The text was updated successfully, but these errors were encountered: