4 ms·

And why is rsync superior?

• pvnick 13y ago
  Part of my reasoning is that rsync is specifically made for this kind of thing, whereas git is specifically made to synchronize coding among multiple developers. So my argument is partly theoretical and less practical. But for an argument based in pragmatism, rsync has tools such as the --delay-updates flag, which allows your entire deployment procedure to become a pass-or-fail atomic operation. This kind of assurance slows my hair loss as a systems administrator. AFAIK git has no such tools, but I'm certainly open to being corrected.
  • statusgraph 13y ago
    Note that delay-updates is not actually atomic [but it's closer] =)
    • pvnick 13y ago
      Good point, thank you!
  • michaelmior 13y ago
    As mentioned in another comment, you can get the rough equivalent of --delay-updates with git fetch followed by git reset or git merge.
  • bretthoerner 13y ago
    The same thing in git: git fetch <remote> && git reset --hard <remote/branch|tag|hash>