Save multiple "preconfigured" "root"-path to select from for left & right side.

[daviank]

I have a configuration file with
- on the left a local path on a local disk
- and on the right a local path to a USB stick (for example) with mount point /media/user/VOLUME_NAME

I would like to use the same configuration but with another USB stick (with volume name = USB_STICK2). The path would then be: /media/user/USB_STICK2

I would also like to use the same configuration with a SFTP path.

If I understand, currently I have to change the path in the right side manually, which is cumbersome, especially to fill the SFTP server every time.

Would it be possible to make this use case simpler? so that if I want to change the path of the right side, I just have to select the correct path that I already configured in the past. I expect the valid paths to be stored in the configuration file.

This would actually also be useful for the left side.

Another use case would be for example to use the same configuration file on both windows & linux. On Windows the configuration file would have c:\path_to_my_files and on linux, it would be something like /mnt/windows_c/path_to_my_files. If these possible values were in the configuration file for easy change, it would be practical.

What do you think?

[Plerry]

You can simply create the correct sync configuration for your first sync, and then save it (Save As, top left) as a *.ffs_gui file under a recognizable, self selected name and in a self selected location.
You do the same for the other two sync configurations.
You then simply select the correct sync configuration from the list in the FFS GUI Configuration window, or you open the intended saved sync configuration form the FFS GUI.

[daviank]

Thank you for the suggestion.

What if I change some configuration/setting of the origial ffs_gui file? My guess is that it will not feed the copy automatically with the changes, and that I will have to replicate all changes to each copy ffs_gui copy manually. This is cumbersome, that's why I suggest to be able to have more than one preconfigured root-path that could be selected (and stored in the ffs_gui file).

With this, it would also for example be possible to use the same ffs_gui file in windows and Linux, whether it is on the same computer or not.

[Plerry]

The presently available alternative in FFS is to create a "parent" sync configuration *.ffs_gui file, that has multiple (in your case: three) left-right pairs (using the green "+"-icon in front of a pair).
And save that "parent" sync configuration as its own *.ffs_gui file.
You could each time open that "parent" configuration, remove the two pairs you do not use then (using the red "-"-icon in front of a pair) and run the sync on the remaining pair.
Or, you can use the parent to make all common changes, save it, and from the "parent" create and save the individual "child" sync configurations.

There is a further alternative: save a *.ffs_gui sync configuration for e.g. your first left-right pair, and invoke your sync from the Command Line, in which you specify said *.ffs_gui sync config, and "overwrite" the saved left-right pair using the -Dirpair option.

FFS sync configurations should be fully portable between Windows and Linux, except for your left-right pair definitions. (Changes you may have made to your global settings, as saved in your GlobalSettings.xml-file, need to be ported separately).
But regarding left-right pairs: obviously c:\path_to_my_files vs /mnt/windows_c/path_to_my_files will not adapt automatically.

[daviank]

Thank you for the suggested workflows. The first one would fit.

As per:

But regarding left-right pairs: obviously c:\path_to_my_files vs /mnt/windows_c/path_to_my_files will not adapt automatically.

I didn't expect automatic transformation between c:\path_to_my_files and /mnt/windows_c/path_to_my_files . My demand was just about being able to have different possible values in the pair, including paths that have no sense for the OS currently running. If I can have multiple pairs, one with windows-style path "C:\..." and one with unix-style path "/mnt/...." it's fine for my use case. Before sync, I would only keep the pair that makes sense for the present OS.