3 ms·
They won't hit all your needs but consider one or more of: 0. https://librsync.github.io/ https://librsync.github.io/ (used by dropbox and used in rdiff-backup
by emmelaich 9y ago
They won't hit all your needs but consider one or more of:
0. https://librsync.github.io/ https://librsync.github.io/ (used by dropbox and used in rdiff-backup, duplicity, ,...)
1. https://github.com/axkibe/lsyncd https://github.com/axkibe/lsyncd (from a google engineer)
2. https://www.cis.upenn.edu/~bcpierce/unison/ https://www.cis.upenn.edu/~bcpierce/unison/ (the B Pierce)
3. Just rsync or rclone[a] in a loop or triggered with incron (http://inotify.aiken.cz/?section=incron&page=about&lang=en http://inotify.aiken.cz/?section=incron&page=about&lang=en)
a. https://rclone.org/ https://rclone.org/
- emmelaich 9y agops. Just found this in the ostree mailing list: https://mail.gnome.org/archives/ostree-list/2018-February/msg00032.html https://mail.gnome.org/archives/ostree-list/2018-February/ms... >> "Is ostree able to generate some kind of binary file containing the required diffs to get from one commit to another, which can be transferred to / copied on the ostree-host and then applied to the repository (similar to a git patch)? > This is what `ostree static-delta generate --filename` will do, combined with `ostree static-delta apply-offline`"