Hi! π
The current workflow uses Unison for bidirectional file sync. I came across Mutagen and think it could be a nice alternative worth considering.
Why Mutagen over Unison?
- Zero remote setup β Mutagen auto-installs its agent binary on the remote via SSH on first connect. Unison requires manually installing a compatible version on both sides (historically even requiring the exact same compiler version, though 2.52+ improved this).
- Always-on daemon with native filesystem watching β Mutagen's sync loop is a persistent daemon using OS-native events (FSEvents / inotify) with accelerated partial scans, giving sub-second sync latency. Unison is fundamentally batch-oriented; its
repeat=watch mode bolts on an external monitor process, adding overhead.
- Built-in Docker container support β
mutagen sync create ~/local docker://container/path just works. Unison has no Docker transport.
- Built-in network forwarding β TCP/Unix socket port forwarding is bundled in, handy for accessing remote services during development. Unison doesn't offer this.
Hi! π
The current workflow uses Unison for bidirectional file sync. I came across Mutagen and think it could be a nice alternative worth considering.
Why Mutagen over Unison?
repeat=watchmode bolts on an external monitor process, adding overhead.mutagen sync create ~/local docker://container/pathjust works. Unison has no Docker transport.