Ignore files older/younger than date

[ciper]

I am using synchting between two android devices. For a specific folder i would like to write an ignore config so that only files older than a certain number of days are synchronized. Is this currently possible or maybe a future ability? Thanks

[calmh (Jakob Borg)]

No, sorry, name based only.

[ciper]

Thanks for the lightening fast reply. Is there a place to submit feature requests? For archival storage on slow media it would be perfect to have date based rules. This would also allow recent files younger than a certain date to be kept on faster (more expensive) storage

[tomasz86]

This has already been proposed multiple times (and rejected). I’d suggest to write a script that would simply add those older files to the ignore patterns automatically, and then set it to run periodically.

[ciper]

The types of files im using it for currently are small and numerous so a script could work but wouldn’t be as robust or elegant as a date filter.

As a new user I wasn’t aware this had been previously discussed. However if people are still showing a desire for such a feature I hope the development team would give it a second consideration. It could be implemented in the gui rather than the ignore file if that makes a difference

[calmh (Jakob Borg)]

date/age ignore pattern

Hi Syncthing gurus! Thanks for making such a great product! As a power user who frequently uses an /Archive* subfolder in my ignore patterns to store older files/folder that I wish not to sync to the clients any longer. Would it be possible to have a date-based ignore pattern? This could be defined similar to a -mtime or -atime or -ctime in a unix find command. It could be a tag on a specific sub-folder/path. A global filter for all members in the folder: -mtime +30d For a specific sub-fol…

Filter files by properties like size, age etc.

Continuing the discussion from Excluding files from synchronization (ignoring):

Feature requests: symlinks, include list, more filter options

I’d like to make three suggestions for inprovements: 1. Symlinks: I know that following symlinks can be a security risk, but on the other hand, it would be a great relief in many cases. E.g., if there’s a directory containing 100 sub-dirs, of which you need to sync just 10 directories. You can, of course, create 10 pairs of dirs to be synched. This will work, of course, but it any of those 10 dirs needs to be swapped by another, you will have to delete one synched pair and create another one. …

[tomasz86]

Yeah, you should be able to find all the older topics if you search the forum for “ignore date”. I wouldn’t have hopes to have this implemented personally .

When it comes to the script though, a possibly clean approach could be to include only younger files and ignore everything else, e.g.

!file1
!file2
*

and so on. A possible problem with this approach is that when one of those included files becomes “old”, there is no simple way to delete it on remote devices only while also keeping a local copy.