Synchronization can result in a corrupted repository. Operations on the remote repository are no longerĪtomic, and concurrent operations or unlucky timing with Special handling for Git repositories, it doesn’t maintain the same The root cause of these problems is that the Dropbox desktopĬlient is designed for syncing files, not Git repositories. Anish (the creator of the library) explains it best: The right way to do this is use git-remote-dropbox: Ĭreating your own bare repo in Dropbox causes a lot of problems.
It’s based on my Ruby on Rails development experience, but it can be applied to anything, really. I wrote a blog post “ On Version Control” in which I cover the reasoning behind my environment setup. ~/project $ git remote add origin ~/Dropbox/git/project.gitįrom there, you can just clone that ~/Dropbox/git/project.git directory (regardless of whether it belongs to your Dropbox account or is shared across multiple accounts) and do all the normal Git operations-they will be synchronized to all your other machines automatically. ~/Dropbox/git $ git init -bare project.git Setup is something like this: ~/project $ git init Since I don’t want to host it on a public service, and I don’t have access to a server that I can always SSH to, Dropbox takes care of this by syncing in the background (very doing so quickly). I have multiple computers (two at home and one at work) on which I use Dropbox as a central bare repository.
0 kommentar(er)
