Git with Dropbox Issues

As it was already pointed out, Dropbox isn’t the safest solution to share your repo (see “Is this plain stupid: GIT Sharing Via DropBox?“.

Greg Bacon remarked that Dropbox already retains old versions of files, which is a bit redundant with what Git already does.

See “this discussion” (which was about a full repo backup, not just a bare repo though):

Well, Dropbox is known for becoming slow when syncing lots of files and Git, by design, creates lots of files on your harddrive. You can encourage packing those many loose objects into few packed objects by running git gc on a regular basis though.

Also Dropbox will start syncing stuff as soon as you do basically anything: checkout, stash, commit, fetch, rebase, reset etc. I’d fear that if I was working too fast, Dropbox would start creating conflicted copies of my files.

Even worse, Git’s internal storage is even more fragile (Git is by no means a backup method!) and because Dropbox was designed to handle your average .doc files, it is just too careless when it comes to manipulating files or filenames. If something in there fails, you might see yourself out of luck.

I use dropbox with a git bundle: only one file to synchronize.
Much less issues that way (but that also means that local setups like hooks aren’t part of my bundle).

Leave a Comment