git-remote-dropbox

For what it's worth, git also can fail in some pretty bizarre ways in Dropbox for much the same reasons. I've used git-remote-dropbox [1] in the past to use Dropbox as a git server. [1] https://github.com/anishathalye/git-remote-dropbox

Isn't there already a good way to push computation closer to the data? GmailFS and pyfilesystem (userspace FUSE) and rclone are neat as well. https://stackoverflow.com/questions/1960799/how-to-use-git-a... explains about the `git push` step that git-remote-dropbox enables: https://github.com/anishathalye/git-remote-dropbox

So, if you really want to use dropbox for syncing git repos, this plugin solves the problem well: 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.

I've never used Github for personal, closed-source projects, but if you have and want to switch to something that provides absolutely no features except git hosting, here are 3 I've used: - Keybase git: https://keybase.io/blog/encrypted-git-for-everyone (my preferred solution these days). - AWS CodeCommit: https://aws.amazon.com/codecommit/ ("encrypted", but I don't know if AWS employees can access it). - Dropbox git remote: https://github.com/anishathalye/git-remote-dropbox (it's slow and unencrypted, but uses Dropbox).

Check if https://github.com/anishathalye/git-remote-dropbox fits your workflow.

For those reading, you should under no circumstances use Dropbox as git hosting unless you're using git-remote-dropbox: https://github.com/anishathalye/git-remote-dropbox Hosing your repo is way too easy otherwise.

I've been using Dropbox as a real handy remote git host using the fantastic git-remote-dropbox utility. It's really great to create a remote repo right from the command line and immediately push to it without the hassle of going to a site like GH or BB and setting up the repo first and all that jazz. Make DB worth the money I spend (and unlimited private repos, of course, and with easy sharing by many developers with Dropbox's shared folders). https://github.com/anishathalye/git-remote-dropbox

Studying the design document [1], one sentence makes it clear why this project is needed and simply using the Dropbox client does not suffice: > We can perform a compare-and-swap operation in Dropbox by using the "update" write mode with a specific revision number. Since a Git repository basically consists of a hash-addressed content object store alongside a mutable list of references (mapping branch names to hashes of latest commits), you need a compare-and-swap operation on the reference list to update the branch reference when you push new commits. The Dropbox client by design does not do a compare-and-swap whenever a file is updated, but the Dropbox API supports it. [1] https://github.com/anishathalye/git-remote-dropbox/blob/mast...

Looks good, I had previously used Dropbox for personal repositories, but now I might try using them for shared ones. It seems from a quick read of the design document [1] that the important thing here is the updating of refs using a compare-and-swap, ensuring that the synchronisation issues that typically occur with using Dropbox as a remote cannot occur. Objects are always* safe from this since the file names are SHA1 hashes. Edit: The only downside I can see with this is that the remote will never have garbage collection take place, so unreachable objects will continue to take up space indefinitely. [1]: https://github.com/anishathalye/git-remote-dropbox/blob/mast...