Changes for version 0.002.2 - 2026-11-18

  • Bug Fixes
    • When the server refused a request that carries data (a delta signature, an upload chunk), it closed the connection without reading that data, so the client could fail with "Broken pipe" instead of showing the reason. This happened mostly on Windows. The server now reads the data before it replies.
    • A server repo created with "--trash-days 0" pruned its trash after 30 days, while a client's "local_trash_days": 0 kept its trash forever. 0 now means "keep forever" on both sides, and the documentation says so. "filesync-admin repo show" prints "kept forever" for such a repo instead of "0 days".
    • "filesync-admin repo show" printed "0 files / 0%" for a repo whose deletion limits are switched off, which read as "nothing may be deleted". It now says "no file limit", "no percentage limit", or "none (any number of deletions)" when both are off.
    • "filesync-admin repo create --max-delete-percent" accepted values over 100. It now refuses anything above 100, and so does the deletion check when a policy file holds such a value.
    • A bad argument was reported in Params::Validate::Strict's own English, naming the internal parameter: "Admin::repo_create: Parameter 'trash_days' (-1) must be at least 0". It is now a catalogued message, and the programs name the option that was typed: "--trash-days must be at least 0, not -1".
    • A directory that became a file could not be synced if it still held an ignored file (a .DS_Store, say): the sync failed with "Cannot replace non-empty directory", then and on every later run. The directory, with whatever the sync does not track, now goes to the trash (the server's or the client's local one) and the file takes its place. The server journals it; the client logs a warning naming the trash.
    • An error the server sent a client named where the server keeps its files ("Cannot create a temporary file in /srv/filesync/master/docs/sub"). A path in the master is now given relative to the repo ("in sub"), and any other server path starts with "[server root]". The server's log is written the same way, since over ssh its standard error reaches the client; the journal keeps the full paths.
    • The server accepted a "mkdir" request for a path whose planned action was a conflict the client's file had won, which no client sends: a client wins a conflict only with a file, and uploads it. Such a request is now refused like any other outside the plan.
  • Documentation
    • "filesync-admin help", the repo_create POD and the website now describe the repo create options, and say that a --max-deletes or --max-delete-percent of 0 switches that deletion limit off.
    • The deletion limits are documented as they behave: both are inclusive (a sync may delete exactly --max-deletes files), and the percentage limit rounds down but always allows one file.
    • filesync-server documents its exit status: 0 after a finished session, 1 after any other.
  • Build
    • META.json says dynamic_config 1, since Win32API::File is required only on Windows; it said 0, so an installer could skip Makefile.PL and miss it.
    • A regression test that builds a 20 MB file runs only with EXTENDED_TESTING set (or on GitHub Actions), so it does not burden CPAN smokers.

Documentation

keep a directory in step with a master copy
administer a filesync server root
serve one sync session (the forced command in authorized_keys)

Modules

cron-driven file synchronisation without a daemon
server-side repo, client and recovery administration
validated arguments for App::FileSync's public routines
shared i18n behaviour for App::FileSync objects
the filesync, filesync-admin and filesync-server commands
sync one repo, and the client-side repo commands
client and repo configuration files
shared constants for App::FileSync
rsync-style block deltas in pure Perl
message catalogue and error raising for App::FileSync
the English message catalogue
filesystem primitives for App::FileSync
.gitignore-style path exclusion
advisory lock files
three-way merge of base, client and master manifests
choose platform workarounds before other modules load
start and reap a transport's child process
the line-delimited JSON wire protocol
describe a directory tree as a manifest
serve one sync session against a repo's master
process-wide settings and logging for App::FileSync
daily snapshots of a replica
the server-side files of one repo
run the server as a local child process
run the server over ssh
dated trash with retention
check a tree against its recorded manifest