This is version 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 . It is not the current version, and thus it cannot be edited.
[Back to current version]   [Restore this version]

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. Its recommended to do at least 3 revisions. If a conflicting edit was done on the same file by two people, it uses the revisions to pull back prior versions so that the users can self resolve the issue.

This configuration is the same on both user1 and user2 in the example.

---

Downloading and Starting the Client#

---

When a user is logged into the WebInterface, you will see an icon next to the folders and files that are being synched. You can click the button to download the sync client if it has been added onto your user in the User Manager. You will be asked for a password, use something secure, this password will be needed every time you open the sync manager to control your sync agent(s).

On windows, you will have an icon in your system tray for the sync agent. On OS X you will have an icon in your dock.

---

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 Sync#

---

The 'Test' button will check your settings and verify a connection to the server to make sure all seems OK.

Now you can click 'Start Sync' to starting things off. It will compare your current files with the server, and look for any changes that have occurred while you were offline.

Once all comparisons are done, it will sit idle in an 'Active' green window state. The realtime file monitor is watching for any changes occurring in the folder you have configured. Any changes, renames, deletes, etc will then be propagated to the CrushFTP server so that other CrushSync clients can replicate them locally.

---

Synchronized#

---

Here is a screenshot of OS X and Windows keeping the files in sync. One file was added on OS X, and the other on Windows, and they were cross replicated between the two different operating systems