CrushSync is an enterprise only feature. It provides real time file synchronizations through CrushFTP. The client runs on the local machine monitoring the specified folders. When a change is detected, the change is propagated to the CrushFTP server, and any other clients subscribed to that folder now get those same changes. Only the changed parts of large files are sent, compression is used to save on bandwidth, and bandwidth acceleration can be used as well. Client configurations can be pre-configured for deployment, and an advanced mode allows clients to encrypt the data at the client side so that the server can never access the raw data. Only clients that have the private key can. This allows for robust one way synchronizations where a client places a file in the folder, and its sent to the server encrypted, and downloaded and decrypted by other privileged clients. The client is launched as an automatically updating application over a web connection. You as the server administrator control when you want to update the application for end users.
Setup Guide: Synching and Revision Tracking
First you need to configure a folder in the user manager that has synchronization tracking enabled on it. Then on a folder item, give it full permissions.
Then click the Advanced button to open the panel to configure the sync options.
This configuration is the same on both user1 and user2 in the example.
Downloading and Starting the Client
Use a URL pointing at your own server something like this:
https://test.crushftp.com/WebInterface/CrushSync/CrushSync.jnlp
This will start a java WebStart application which is the client. Its downloaded automatically, and launched after getting user approval.
OS X:
Windows:
You may be prompted to save a shortcut for future launching of the application without going to the URL again. If you are not prompted, it will save a shortcut icon on your desktop.
Configuring the Client
The client needs to be configured to connect to your CrushFTP server. You can build a default configuration that gets distributed automatically with CrushSync downloads so that the user only need to enter in details like their username and password. You can take a look at the jnlp file in the WebInterface/CrushSync/ folder to see the reference it makes for a default configuration file.
Otherwise, you can configure everything in the client.
OS X:
Windows:
There needs to be a local folder configured for synchronization, as well as the server path. Typically this is going to just be a single slash unless you are only synching to a sub directory of a user.
The path to the server location must always be the same across multiple accounts. So user1 can't have a server path of /myfiles/ and user2 have a path of /mydocuments/. They both must be the same.
Testing and Starting the Synch
The
Add new attachment
List of attachments
Kind | Attachment Name | Size | Version | Date Modified | Author | Change note |
---|---|---|---|---|---|---|
png |
config_user1_osx.png | 52.2 kB | 1 | 25-Oct-2018 04:31 | Ben Spink | |
png |
config_user2_win.png | 109.5 kB | 1 | 25-Oct-2018 04:31 | Ben Spink | |
png |
crushsync-download_osx.png | 49.6 kB | 1 | 25-Oct-2018 04:31 | Ben Spink | |
png |
crushsync-download_win.png | 37.0 kB | 1 | 25-Oct-2018 04:31 | Ben Spink | |
png |
crushsync.png | 56.0 kB | 3 | 25-Oct-2018 04:31 | Ben Spink | |
png |
crushsync_active.png | 99.9 kB | 1 | 25-Oct-2018 04:31 | Ben Spink | |
png |
crushsync_osx_win.png | 312.7 kB | 1 | 25-Oct-2018 04:31 | Ben Spink | |
png |
file_upload_osx.png | 124.0 kB | 1 | 25-Oct-2018 04:31 | Ben Spink | |
png |
saving_shortcut_app_osx.png | 33.2 kB | 1 | 25-Oct-2018 04:31 | Ben Spink | |
png |
sync_webinterface.png | 47.0 kB | 1 | 25-Oct-2018 04:31 | Ben Spink | |
png |
test_sync.png | 133.2 kB | 1 | 25-Oct-2018 04:31 | Ben Spink | |
png |
usermanager_vfs_sync.png | 132.0 kB | 2 | 25-Oct-2018 04:31 | Ben Spink | |
png |
vfs_sync.png | 32.7 kB | 1 | 25-Oct-2018 04:31 | Ben Spink | |
png |
windows_synched_file.png | 133.1 kB | 1 | 25-Oct-2018 04:31 | Ben Spink |