HandyCafe Docs
it-admin

File Sync

File Sync distributes files from the HandyCafe Server to client PCs across the network. Use it to push game updates, configuration files, software installers and client menu assets without visiting each machine.

It uses a manifest-based approach so that only changed or new files travel over the wire, which keeps repeated syncs fast.

The page is at Settings > File Sync.

Enable Client Sync

A toggle at the top right of the page controls the whole feature. While Enable Client Sync is off, the page reports that client sync is paused and both publish and delete actions are blocked. Turn it on before you publish anything.

Publish a Sync Source

The Publish Sync Source section is where a sync is created. It takes two values:

Field What it is
Source Path The file or folder on the server that you want distributed. Use Pick File or Pick Folder to choose it, or type the path directly.
Target Path On Clients The absolute path where the content must land on every client. This is not optional. Example: C:\Games\SteamLibrary\common\Game or /opt/apps/game.

The target path has to be valid on the client machines, not on the server. If your clients keep their games on D: and you enter a C: path, the sync lands in the wrong place.

Select Publish Sync once both fields are filled. The content is served to clients directly from the source path. The server keeps no second copy.

How Synchronization Works

Manifest-Based Comparison

When a sync begins, the server generates a file manifest: a list of every file to be synced along with its checksum. Each client compares this manifest against its own local files.

  • Files that do not exist on the client are marked for download.
  • Files whose checksums differ (meaning they were modified) are marked for download.
  • Files that match are skipped entirely.

Only the delta between server and client is transferred, which is what makes repeated syncs fast.

Chunk-Based Transfer

Large files are split into smaller chunks for transfer over TCP:

  • Reliability. If a chunk fails, only that chunk is retried rather than the whole file.
  • Progress tracking. Transfer progress is reported at the chunk level.
  • Network efficiency. Chunk sizes are tuned for typical LAN conditions.

Transfers use the dedicated File Port from Network Settings, 5002 by default. If that port is blocked by a firewall, no file will reach the clients.

Synced Folders

The Synced Folders list shows one row per target path, each with its most recent published release. A row reports the release count, the file count and the total size. Use Refresh to reload the list.

Select a row to open its details on the right. The detail panel lists every entry in that source with its path, kind (file or directory), size and checksum, along with the source root path, target path and publish time. The search box filters entries by relative or target path.

Removing a Sync

Two different delete actions exist. They do different things:

  • Remove Synced Folder takes the target path off the sync list. Your source files on the server are not touched.
  • Delete Entry removes an item from the original source path on the server. This is permanent and it is also pushed to clients. HandyCafe asks for confirmation first.

Both actions require Enable Client Sync to be on.

Use Cases

  • Deploying game updates. Push game patches to all gaming PCs at once so every machine runs the same version.
  • Pushing configuration files. Distribute updated network settings or application preferences across all clients.
  • Distributing software. Install applications on client PCs by syncing installer packages or portable applications.
  • Updating client menu assets. Sync new icons, posters or media files used by the client menu.

Tips

  • Schedule large syncs during off-peak hours so active sessions are not competing for bandwidth.
  • Double-check the target path before publishing. It is the single most common cause of a sync that appears to succeed while nothing shows up on the client.
  • The server and clients must be on the same LAN.

Related Pages