正确的方法是使用git-remote-dropbox: https://github.com/anishathalye/git-remote-dropbox

在Dropbox中创建自己的裸回购会导致很多问题。Anish(库的创造者)解释得很好:

The root cause of these problems is that the Dropbox desktop client is designed for syncing files, not Git repositories. Without special handling for Git repositories, it doesn’t maintain the same guarantees as Git. Operations on the remote repository are no longer atomic, and concurrent operations or unlucky timing with synchronization can result in a corrupted repository. Traditional Git remotes run code on the server side to make this work properly, but we can’t do that. Solution: It is possible to solve this properly. It is possible to use Git with Dropbox and have the same safety and consistency guarantees as a traditional Git remote, even when there are multiple users and concurrent operations! For a user, it’s as simple as using git-remote-dropbox, a Git remote helper that acts as a transparent bidirectional bridge between Git and Dropbox and maintains all the guarantees of a traditional Git remote. It’s even safe to use with shared folders, so it can be used for collaboration (yay unlimited private repos with unlimited collaborators!). With the remote helper, it’s possible to use Dropbox as a Git remote and continue using all the regular Git commands like git clone, git pull, and git push, and everything will just work as expected.

我认为Dropbox上的Git很棒。我一直在用它。我有多台电脑(两台在家里，一台在公司)，我把Dropbox作为一个中央的存储库。因为我不想把它托管在公共服务上，而且我也没有可以通过SSH访问的服务器，Dropbox通过在后台同步来解决这个问题(非常快)。

设置是这样的:

~/project $ git init
~/project $ git add .
~/project $ git commit -m "first commit"
~/project $ cd ~/Dropbox/git

~/Dropbox/git $ git init --bare project.git
~/Dropbox/git $ cd ~/project

~/project $ git remote add origin ~/Dropbox/git/project.git
~/project $ git push -u origin master

从那里，你可以克隆~/Dropbox/git/项目。git目录(无论它是否属于你的Dropbox帐户或在多个帐户之间共享)并执行所有正常的git操作-它们将自动同步到你所有的其他机器。

我写了一篇博客文章“关于版本控制”，其中介绍了环境设置背后的原因。它基于我的Ruby on Rails开发经验，但实际上它可以应用于任何东西。

我使用Mercurial(或Git) + TrueCrypt + Dropbox进行加密远程备份。

最酷的是，如果你修改了一小部分代码，Dropbox不会同步整个TrueCrypt容器。同步时间大致与更改量成比例。即使它是加密的，TrueCrypt + Dropbox的组合也很好地利用了块密码+块级同步。

其次，单片加密容器不仅增加了安全性，还减少了存储库损坏的可能性。

警告:但是你必须非常小心，不要在Dropbox运行时挂载容器。如果两个不同的客户端将不同的版本签入到容器中，解决冲突也会很麻烦。因此，它只适用于个人备份，而不适用于团队。

设置:

创建一个Truecrypt容器(多个gb就可以了) 在Truecrypt首选项下，取消选中保留修改时间戳*。 创建一个由Dan上面提到的回购(https://stackoverflow.com/a/1961515/781695)

用法:

Dropbox辞职 挂载容器，推送更改，卸载 dropbox运行

附注:取消选中保留修改时间戳告诉dropbox文件已被修改，它应该同步。注意，即使不更改容器中的任何文件，装入容器也会修改时间戳。如果不希望发生这种情况，只需将卷挂载为只读

正确的方法是使用git-remote-dropbox: https://github.com/anishathalye/git-remote-dropbox

在Dropbox中创建自己的裸回购会导致很多问题。Anish(库的创造者)解释得很好:

The root cause of these problems is that the Dropbox desktop client is designed for syncing files, not Git repositories. Without special handling for Git repositories, it doesn’t maintain the same guarantees as Git. Operations on the remote repository are no longer atomic, and concurrent operations or unlucky timing with synchronization can result in a corrupted repository. Traditional Git remotes run code on the server side to make this work properly, but we can’t do that. Solution: It is possible to solve this properly. It is possible to use Git with Dropbox and have the same safety and consistency guarantees as a traditional Git remote, even when there are multiple users and concurrent operations! For a user, it’s as simple as using git-remote-dropbox, a Git remote helper that acts as a transparent bidirectional bridge between Git and Dropbox and maintains all the guarantees of a traditional Git remote. It’s even safe to use with shared folders, so it can be used for collaboration (yay unlimited private repos with unlimited collaborators!). With the remote helper, it’s possible to use Dropbox as a Git remote and continue using all the regular Git commands like git clone, git pull, and git push, and everything will just work as expected.

我把我的非github回购存储在Dropbox上。我遇到的一个警告是重新安装后的同步。Dropbox会先下载最小的文件，然后再下载较大的文件。如果你从晚上开始，周末后再回来，这不是问题:-)

我的帖子- http://forums.dropbox.com/topic.php?id=29984&replies=6

在不使用第三方集成工具的情况下，我可以稍微改善一下条件，并使用DropBox和其他类似的云磁盘服务，如带Git的SpiderOak。

我们的目标是避免在这些文件修改的中间同步，因为它可以上传一个部分状态，然后下载回来，完全破坏你的git状态。

为了避免这个问题，我做了:

使用git Bundle create my_repo将我的git索引捆绑在一个文件中。git——所有。 为文件监控设置一个延迟，例如5分钟，而不是瞬间。这降低了DropBox在更改过程中同步部分状态的机会。它在动态修改云磁盘上的文件时也有很大帮助(比如即时保存笔记应用程序)。

它并不完美，因为不能保证它不会再次弄乱git状态，但它有帮助，目前我没有遇到任何问题。