5 ms·
I had the exact same thing, granted, it was ten years ago already, with dropbox. Something something file versioning, ending up with neighboring files of confli
by WesolyKubeczek 5y ago
I had the exact same thing, granted, it was ten years ago already, with dropbox. Something something file versioning, ending up with neighboring files of conflicting revisions, the disease spreading over to all instances.
My takeaway was „never keep git repos in a system that does its own distributed versioning”. I just do git push around so my remotes are up to date. Git is sort of dropbox with a manual gearbox, after all (and more, but that’s not the point).
I’m really unsure that this is a kind of easily solvable problem for either dropbox or syncthing. Unless your syncing product gets smart enough to understand what a git repository is and how some files have to be checked in in lockstep, that is. Otherwise, expect race conditions.
- banana_giraffe 5y agoSo, if you really want to use dropbox for syncing git repos, this plugin solves the problem well: https://github.com/anishathalye/git-remote-dropbox https://github.com/anishathalye/git-remote-dropbox For me, it solved all of the corruption problems with using Dropbox for git storage. In the end, I decided it was too heavy weight, and wanted to be able to clone my repo on machines that might not have anything other than "git" installed, but until I reached that point, I was a happy user of it. I'm not aware of a similar tool for syncthing.