I like the idea of staggered file versioning - that is, keeping time-based increments of my files, constrained by time intervals rather than just an arbitrary number. However, I find it’s currently way too aggressive by default. For the first hour, a version is kept for every 30 seconds; for the first day, a version is kept every hour, and so on. I have a single 90 MB file that gets written to very frequently, and so within a day it’s already ballooned to 2.7 GB.
I’m trying to configure it so that instead of having a max of 120 copies in the first hour, it just keeps one copy for the first hour. Instead of having 24 copies in the first day, it just has one copy for the first day, and so on. Is this possible?
The intervals are hard-coded, so the only way is to modify the source code and compile your own version of Syncthing. This is what I’ve actually been doing for quite a while, as I don’t like the default intervals as well.
Otherwise, as already mentioned, you can re-implement the whole logic with custom scripts, etc. but it’s going to be quite complicated, and you’d also need to implement your own version cleanup routine on top of that .
Alright, thanks! This would be nice as a feature someday, but for now both of these are a little bit outside of my skill-set, especially as I’d have to get it going for multiple platforms and it’s probably not really worth the effort for my usecase. Still, I appreciate the explanation!
.