Storing .git folders in dropbox doesn't seem like the best idea. You could keep a git repository in a different location and have a small build script like this https://github.com/minhajuddin/notes.minhajuddin.com/blob/ma... which builds your website and copies it to a dropbox folder. With this approach you could even use something like http://middlemanapp.com/.
I have 2+ side projects or submodules under development at any given time. I've been storing them in Dropbox for the last 3 years. I've been working on them actively from 3 different machines (two Ubuntu desktops and one OS X laptop), and they're turned off -- so not syncing -- when I'm not using them.
All that said, I haven't had one single problem. So empirically speaking, I don't see any problem with the mechanics of .git folders in Dropbox.
(Note that my key files, API keys, etc. are not synced to Dropbox.)
I have had many instances of copies of files being created when there is a conflict. This shouldn't happen if the syncs happen before you work on a file (which is your situation). The main issue for me is that dropbox doesn't explicitly tell you that there is a conflict, it just creates a file with the other machine's name and you may end up scratching your head for a long time before figuring out about the conflict.
To be honest, I haven't tried storing git repos on Dropbox so these are just my assumptions based on dropbox usage for other files. I am just afraid that it may end up corrupting my git repo.
I have 2+ side projects or submodules under development at any given time. I've been storing them in Dropbox for the last 3 years. I've been working on them actively from 3 different machines (two Ubuntu desktops and one OS X laptop), and they're turned off -- so not syncing -- when I'm not using them.
All that said, I haven't had one single problem. So empirically speaking, I don't see any problem with the mechanics of .git folders in Dropbox.
(Note that my key files, API keys, etc. are not synced to Dropbox.)