You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The versioning system in SyncThing is great, but sometimes one does not want to version everything. In my case it is a Thunderbird profile folder that (for backup purposes) is sync'd as part of a larger parent directory. For that directory and (most of) its subdirectory, versioning is in place. But for the TB Profile directory this results in a lot of space being consumed. Perhaps not the best reason for this feature, but it is a reason...
That feature would be that you can specify (in some way) that some directories need not by versioned, although sync'd. I see roughly two ways of dealing with this: either a file like .stignore containing regex patterns, or the (probably) more simpler approach of allowing the user to create a directory inside the .stversions directory with a marker signalling that that everything in that directory needs not be versioned. Something like:
I could see this happen in lib/versioner/util.go where archiveFile does a check if the directory to move the versioned file to exists and if not, creates it. That could be prepended by a check for the existence of .stdisable_versions in any of the parent directories. I have, unfortunately, not enough knowledge of the Go language to prepare a code block for this.
The text was updated successfully, but these errors were encountered:
Not sure if feasible, but having separate ignore patterns just for versioning could be quite useful. At the moment, you can utilise external versioning with your own script to achieve what you want here.
The versioning system in SyncThing is great, but sometimes one does not want to version everything. In my case it is a Thunderbird profile folder that (for backup purposes) is sync'd as part of a larger parent directory. For that directory and (most of) its subdirectory, versioning is in place. But for the TB Profile directory this results in a lot of space being consumed. Perhaps not the best reason for this feature, but it is a reason...
That feature would be that you can specify (in some way) that some directories need not by versioned, although sync'd. I see roughly two ways of dealing with this: either a file like .stignore containing regex patterns, or the (probably) more simpler approach of allowing the user to create a directory inside the .stversions directory with a marker signalling that that everything in that directory needs not be versioned. Something like:
I could see this happen in lib/versioner/util.go where archiveFile does a check if the directory to move the versioned file to exists and if not, creates it. That could be prepended by a check for the existence of .stdisable_versions in any of the parent directories. I have, unfortunately, not enough knowledge of the Go language to prepare a code block for this.
The text was updated successfully, but these errors were encountered: