[feature request] Extended versioning

Discuss new features and functions
Posts: 1
Joined: 28 Aug 2018

IcePlanet

I would like to propose extended versioning features of the sync.

1. Timestamp format customizable
Add possibility to own format of timestamp. The current one is great, but for all the scripting I'm using more computer readable format YYYYMMDDHHMMSS. It would be great if user can configure format of timestamp.

2. Possibility to zip older versions
It is clear that zip will basically mean twice transfer of the file, but for some use cases this might be very useful. Packaging SW can be part of configuration (e.g. pack via: <path><program><parameters, where #1 indicates file name>) so no need to bundle with program. Only older versions will be packed, current one will be kept as it is

3. Timestamp file in case of older versions
In the settings there should be possibility to indicate what timestamp should be used, if the one from actual time (as-is status) or the 'file' one based on last modification time/date. Purpose of this is that when searching for older version you can search by the time when you have modified the file, not by the time when sync was running.

Sample (with all 3 options included) initial status on source:
27.08.2018  22:18             1 364 File1
27.08.2018  18:47             1 431 File2
After initial sync, the destination will look exactly the same (not shown here). Then change to File 1 is made so new local status will be:
27.08.2018  23:47             1 564 File1
After sync is run the next day (28.08.2018 as 08:00) the destination will look like:
27.08.2018  22:18               795 File1.20180827221800.zip
27.08.2018  23:47             1 564 File1
27.08.2018  18:47             1 431 File2
What do you think about these features?