At line 1 changed one line |
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. |
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, and bandwidth acceleration can be used as well. |
At line 3 added 2 lines |
[CrushSync Comparison] with some other similar products. |
|
At line 4 changed one line |
Example CrushSync configuration with a client on OS X and a client on Windows. |
!!!Setup Guide: Synching and Revision Tracking |
At line 6 removed 2 lines |
__Making the VFS Support Synching and Revision Tracking__ |
|
At line 12 changed one line |
Then click the Advanced button to open the panel to configure the sync options. |
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. |
At line 18 changed one line |
__Downloading and Configuring the Client__ |
!!!Giving Access to the Client |
---- |
The app itself is located here: \\ |
Windows: [https://www.crushftp.com/early10/CrushSync/CrushSync_windows.exe]\\ |
macOS: [https://www.crushftp.com/early10/CrushSync/CrushSync_macOS.zip]\\ |
---- |
!!!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. |
[attachments|sync_webinterface.png]\\ |
At line 20 changed one line |
Use a URL pointing at your own server something like this: |
[attachments|crushsync.png]\\ |
On windows, you will have an icon in your system tray for the sync agent and on OS X you will have an icon in your menubar. There is no management UI on the machine, you do all of that through the WebInterface in the 'Sync Manager'.\\ |
[attachments|crushsync_menu.png] |
|
---- |
!!!Configuring the Client |
---- |
You can configure everything in the client. |
|
[attachments|crushsync_web.png]\\ |
|
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. |
|
---- |
!!!Starting the Sync |
---- |
|
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. |
|
|
---- |
!!!Special, macOS only daemon install requirement |
---- |
macOS can no longer load our 'magical' native library that we use for listening into filesystem events. We have an alternative method, but it requires a one time daemon install command.\\ |
\\ |
First, find your CrushSync folder, and decide where its going to stay...forever, no changes to it, no renaming the folder, etc.\\ |
At line 22 changed one line |
https://test.crushftp.com/WebInterface/CrushSync/CrushSync.jnlp |
cd /Applications/CrushSync_macOS/CrushSync.app/Contents/Resources/ |
sudo Java/bin/java -cp CrushTunnel.jar com.crushftp.client.CrushSyncFSWatchServer -i |
At line 25 changed 2 lines |
OS X: [attachments|crushsync-download_osx.png]\\ |
Windows: [attachments|crushsync-download_win.png]\\ |
Enter your admin password and your done. If you laterened to remove that daemon, change the "-i" to a "-r". |
---- |
!!! Special, Windows service mode install |
---- |
Make sure the "Start with login" option is not set in the tray icon context menu, if it is, remove it. Close CrushSync if it is running. Then open an elevated CMD or PowerShell session, change directory into the installation folder, usually C:\Users\Administrator\AppData\Local\Programs\CrushSync\Resources , issue below command |
{{{ |
.\Java\bin\java.exe -jar CrushTunnel.jar inline_script "service sync;quit" |
}}} |
Check the state of service in the Services console , or from command line |
{{{ |
sc query "CrushSync Server" |
}}} |
|
''Alternatively you can do a simpler install using the CrushTunnel.jar file from your WebInterface folder instead of using that buried deep folder as referenced above. Just be sure to copy your existing prefs.XML into it as you cannot access a systray to configure the service version. |