• General
  • Sharing
  • File Versioning
  • Ignore Patterns
  • Advanced

Optional descriptive label for the folder. Can be different on each device.

Required identifier for the folder. Must be the same on all cluster devices. The folder ID must be unique. The folder ID cannot be blank. When adding a new folder, keep in mind that the Folder ID is used to tie folders together between devices. They are case sensitive and must match exactly between all devices.

Path to the folder on the local computer. Will be created if it does not exist. The tilde character (~) can be used as a shortcut for {{system.tilde}}.
The folder path cannot be blank. Warning, this path is a subdirectory of an existing folder "{%otherFolder%}". Warning, this path is a subdirectory of an existing folder "{%otherFolderLabel%}" ({%otherFolder%}). Warning, this path is a parent directory of an existing folder "{%otherFolder%}". Warning, this path is a parent directory of an existing folder "{%otherFolderLabel%}" ({%otherFolder%}).

Deselect devices to stop sharing this folder with.  Select All  Deselect All

1 The remote device has not accepted sharing this folder.

2 The remote device has paused this folder.

Select additional devices to share this folder with.  Select All  Deselect All

There are no devices to share this folder with.

  Help

Files are moved to .stversions directory when replaced or deleted by Syncthing.

Files are moved to date stamped versions in a .stversions directory when replaced or deleted by Syncthing.

days

The number of days to keep files in the trash can. Zero means forever. The number of days must be a number and cannot be blank. A negative number of days doesn't make sense.

The number of old versions to keep, per file. The number of versions must be a number and cannot be blank. You must keep at least one version.

Files are moved to date stamped versions in a .stversions directory when replaced or deleted by Syncthing. Versions are automatically deleted if they are older than the maximum age or exceed the number of files allowed in an interval.

The following intervals are used: for the first hour a version is kept every 30 seconds, for the first day a version is kept every hour, for the first 30 days a version is kept every day, until the maximum age a version is kept every week.

days

The maximum time to keep a version (in days, set to 0 to keep versions forever). The maximum age must be a number and cannot be blank. A negative number of days doesn't make sense.

Path where versions should be stored (leave empty for the default .stversions directory in the shared folder).

An external command handles the versioning. It has to remove the file from the shared folder. If the path to the application contains spaces, it should be quoted.

See external versioning help for supported templated command line parameters. The path cannot be blank.

seconds

The interval, in seconds, for running cleanup in the versions directory. Zero to disable periodic cleaning. The cleanup interval cannot be blank. The interval must be a positive number of seconds.

Ignore patterns can only be added after the folder is created. If checked, an input field to enter ignore patterns will be presented after saving.

Enter ignore patterns, one per line.

{{ignores.error}}


Quick guide to supported patterns (full documentation):

(?d)
Prefix indicating that the file can be deleted if preventing directory removal
(?i)
Prefix indicating that the pattern should be matched without case sensitivity
!
Inversion of the given condition (i.e. do not exclude)
*
Single level wildcard (matches within a directory only)
**
Multi level wildcard (matches multiple directory levels)
//
Comment, when used at the start of a line

Editing {%path%}.
  Help

Use notifications from the filesystem to detect changed items. Watching for changes discovers most changes without periodic scanning.

The rescan interval must be a non-negative number of seconds.

  Help

Files are protected from changes made on other devices, but changes made on this device will be sent to the rest of the cluster.

Files are synchronized from the cluster, but any changes made locally will not be sent to other devices.

Stores and syncs only encrypted data. Folders on all connected devices need to be set up with the same password or be of type "{%receiveEncrypted%}" too.

Folder type "{%receiveEncrypted%}" cannot be changed after adding the folder. You need to remove the folder, delete or decrypt the data on disk, and add the folder again.

Folder type "{%receiveEncrypted%}" can only be set when adding a new folder.


Enter a non-negative number (e.g., "2.35") and select a unit. Percentages are as part of the total disk size.

Disables comparing and syncing file permissions. Useful on systems with nonexistent or custom permissions (e.g. FAT, exFAT, Synology, Android).

  Help

Enables sending ownership information to other devices, and applying incoming ownership information. Typically requires running with elevated privileges.

Enables sending ownership information to other devices, but not applying incoming ownership information. This can have a significant performance impact. Always enabled when "Sync Ownership" is enabled.

  Help

Enables sending extended attributes to other devices, and applying incoming extended attributes. May require running with elevated privileges.

Enables sending extended attributes to other devices, but not applying incoming extended attributes. This can have a significant performance impact. Always enabled when "Sync Extended Attributes" is enabled.

  Help

To permit a rule, have the checkbox checked. To deny a rule, leave it unchecked.

No rules set

Default: {{getXattrDefault()}}

{{getXattrHint()}}