4 ms·
Do yourself a favor and get a real git repository. Using dropbox is indeed super easy but has two major caveats: 1. Git is agnostic to updates to the repo, as
by yuvadam 16y ago
Do yourself a favor and get a real git repository. Using dropbox is indeed super easy but has two major caveats:
1. Git is agnostic to updates to the repo, as dropbox is not a supported transport method (as opposed to SSH for example). So, for example, git hooks won't work.
2. Dropbox is extremely susceptible to repo corruption in case of simultaneous updates. Restoring a corrupt repo is not a pleasant task.
For your sanity - don't do it.
- fryguy 16y agoWhat I usually do is have multiple repos, one per machine I'm working on. This way they are write-once, read-many so you don't ever have dropbox merge conflicts. It's a bit more overhead, but safer. It's even "easier" to get the semantics right in bazaar due to the branch-as-a-folder paradigm rather than a repo-as-a-folder design of git, although I don't really want to devolve to a "my scm is better than your scm" debate.
- doty 16y agoI think you missed a point in the post: the designers are NOT using git. When the designers make a change, the designers are not doing a git add. Dropbox is just about getting the assets from the designers to the developers, so that the developers can do the appropriate git operations. Presumably the developers have whatever hooks they want, and they still get run at the appropriate time....