In this view set environment. It is possible to enter an environment variable to the process which executes the synchronize task. An example of such is : "SSH_AUTH_SOCK": "/Users/username/.gnupg/S.gpg-agent.ssh"
Use RsyncUI for quickly synchronize files to either local or remote storage. If synchronizing to a remote storage require setup of passwordless login. There are two types of quick tasks: synchronize - synchronize local files to remote syncremote - synchronize remote files to local Caution: if syncremote the localcatalog in the form is the remote data and remotecatalog is the local data where remote data will land when pulled. After entering data, default is a --dry-run task.
Restore either files or complete synchronized files is easy in RsyncUI. A restore has to be executed to a temporary restore path. This is to secure not destroying any original data. A restore session might be as follows. Selecting and filtering First of all select from which configuration to restore from. After selection RsyncUI automatically collects filenames of all synchronized files. The list might be huge and it is adviced to filter data before viewing retrieved filelist if there are several hundred thousand of lines.
You can any time save the current configuration files by the Backup button. The backup button executes a copy of all configuration files into your Documents catalog and postfixes the copy with a timestamp -month-day-year/hour/minute. $HOME/Documents/RsyncUIcopy-05-06-2021/08/21 Caution: when opening the catalog it might be seen as empty. The copy is a .catalog and your filebrowser might not see such catalogs. Rsync version and path It is adviced to install rsync as part of Homebrew.
In this view you can let RsyncUI assist in creating ssh-keys and setup global ssh keypath and identityfile, either utilizing default values or set your own. There is some more info about ssh. Local ssh keys found If on RsyncUI has found local ssh keys. Default values for ssh are ~/.ssh/id_rsa and portnumber 22. It is not required to set your own values for key path and identityfile if default values are used.
A task require minimum a local catalog and a remote catalog. After entering information about a task, select the Add button to add it to RsyncUI. Continue adding new tasks until completed and tasks are saved to permanent storage after each entry. After adding or changed a task please verify the result by executing an estimation run. The following actions within this view: Add - will add a new task Update - the Add button will change when a task is selected Just press the Enter key will automatically enter a new task.
The task view either lets you: execute all or selected (by shortcut ⌘T) tasks in one go for one task, estimate and view the detailed output from rsync before executing the real run All actions are triggered either by keyboard shortcuts or by buttons. The following are allowed shortcut actions: estimate - shortcut ⌘E execute - shortcut ⌘R select task - shortcut ⌘T Several tasks This is most likely the most used action after adding and verifying the task.
If you are new to the command line tool rsync and RsyncUI please read this information. The –delete parameter and new tasks RsyncUI is only a GUI on top of the command line tool and it is rsync which does actual work, not RsyncUI. The --delete parameter is a default parameter set by RsyncUI to rsync. The parameter instructs rsync too keep the source and destination in sync. The parameter instructs rsync to delete all files in the destination which are not present in the source.
You can connect shell scripts to a task. A shell script can e.g. be mounting (pre) and unmounting (post) of a remote storage. Or you can execute a shell script to encrypyt your data ahead of synchronizing the data. It is only possible to execute the shell scripts utilizing Single task and the Now button. Tasks are marked if there are shell scripts connected to the task. The shell scripts names and locations is selected by the user.
There are two ways to setup passwordless logins to a remote server. RsyncUI supports both. It is strongly advised to use ssh and ssh-keys because the traffic is encrypted and it is considered more secure. Encrypted protocol by ssh and ssh-keys Using ssh-keys is in general considered more safe than standard password solutions (single factor authentication). Ssh-keys are based upon public-key cryptography. RsyncUI can assist you in setting up passwordless logins Rsync transfer data between client and server by tunneling transfer of data in an encrypted ssh tunnel.