| 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 |
| __Setup Guide: Synching and Revision Tracking__ |
| !!!Setup Guide: Synching and Revision Tracking |
| At line 10 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 16 changed one line |
| __Downloading and Starting the Client__ |
| !!!Giving Access to the Client |
| At line 18 changed 4 lines |
| Use a URL pointing at your own server something like this: |
| {{{ |
| https://test.crushftp.com/WebInterface/CrushSync/CrushSync.jnlp |
| }}} |
| 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 23 changed one line |
| This will start a java WebStart application which is the client. Its downloaded automatically, and launched after getting user approval. |
| [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] |
| At line 25 changed 4 lines |
| OS X:\\ |
| [attachments|crushsync-download_osx.png]\\ |
| Windows:\\ |
| [attachments|crushsync-download_win.png]\\ |
| ---- |
| !!!Configuring the Client |
| ---- |
| You can configure everything in the client. |
| At line 30 changed one line |
| 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. |
| [attachments|crushsync_web.png]\\ |
| At line 32 changed one line |
| [attachments|saving_shortcut_app_osx.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. |
| At line 42 added 2 lines |
| 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. |
|
| At line 35 changed one line |
| __Configuring the Client__ |
| !!!Starting the Sync |
| At line 37 removed one line |
| 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. |
| At line 39 changed one line |
| Otherwise, you can configure everything in the client. |
| 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. |
| At line 41 changed 4 lines |
| OS X:\\ |
| [attachments|config_user1_osx.png]\\ |
| Windows:\\ |
| [attachments|config_user2_win.png]\\ |
| 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. |
| At line 46 removed one line |
| 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. |
| At line 48 removed 2 lines |
| 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. |
|
| At line 51 changed one line |
| __Testing and Starting the Synch__ |
| !!!Special, macOS only daemon install requirement |
| At line 56 added 7 lines |
| 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.\\ |
| {{{ |
| cd /Applications/CrushSync_macOS/CrushSync.app/Contents/Resources/ |
| sudo Java/bin/java -cp CrushTunnel.jar com.crushftp.client.CrushSyncFSWatchServer -i |
| }}} |
| At line 54 changed one line |
| The |
| 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" |
| }}} |
