Skip to content
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

Synchronization Filter File #4495

Closed
cyberduck opened this issue May 25, 2010 · 1 comment
Closed

Synchronization Filter File #4495

cyberduck opened this issue May 25, 2010 · 1 comment

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented May 25, 2010

rareyman created the issue

I love that Cyberduck uses Filters in Preferences to exclude things during upload and download! However, sometimes I need to exclude files on a "per folder" basis. I may have a number of large files on the server that I do not need to synchronize to my local drive, but I need to synchronize everything else. In this case Synchronize doesn't work for me.

I think it would be great to have a Synchronization Filter File that can be used in addition to the settings in preferences, on a "per folder" basis. I envision it working like this:

We create a file in each folder being synchronized:

cyberduck-sync.txt (this file is always ignored during synchronization process)



cyberduck-sync.txt (local folder) is a regular expression of items to avoid during the upload/mirror synchronization process

cyberduck-sync.txt (ftp site) is a regular expression of items to avoid during the download/mirror synchronization process

If the two files are in place, now when I synchronize the two folders, in addition to the filter settings in Preferences, it also honors the regex filters in the "cyberduck-sync.txt" files for upload and download when running the synchronization process.



This could get tricky when folders are nested inside other folders:


A/AA/cybersync.txt <-> B/BB/cybersync.txt


If you sync A <-> B does cyberduck honor the cybersync.txt of AA and BB?

My guess is not, but if this is a caveat the user knows about, it can be dealt with.

Anyway, I just thought it'd suggest a new feature that hopefully isn't super difficult to implement, but could be really useful for us Cyberduck sync users!

Thanks!

R

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented May 30, 2010

@dkocher commented

Thanks for your detailed enhancement request. I don't have currently any plans to support such more fine grained but proprietary synchronization methods.

Loading

@cyberduck cyberduck closed this May 30, 2010
@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants