HN

Comments (4)

• Menu

  yjftsjthsd-h
  Promising; kinda feels like a hopefully-better syncthing, albeit I think one-direction?Anyways, some hopefully constructive questions that I don't see in the readme:* Is sync done in cleartext? (Or am I misunderstanding the model and this expects you to handle the network layer yourself with eg. NFS?)* How are conflicts handled?* Actually, in general where does this land on CAP? (There's a section titled "Consistency" but it doesn't really answer what I want to know)> If enable_versioning is active, the daemon creates zero-cost reflink snapshots on fsync:* How does it handle filesystems that doesn't have that feature? (XFS and BTRFS are easy, but this says it supports ext4)(And to be clear, none of these are meant as criticisms of the actual software; they're things that the user should know the answer to, not questions that have to have a specific answer)
• mrbluecoat
  How would you replicate: rsync -avz -e "ssh" user@remote_host:/path/to/source/ /path/to/destination/Something like this? fxcp snap export /path/to/source/ | ssh user@remote_host -t 'fxcp snap import /path/to/destination/'
• copper-float
  No, Foxing is one of my favorite indie-rock bands from the St. Louis area.