What I described here is only one possible workflow to give you an idea of how such a workflow could look like. You can find other workflows in the Pro Git book. In the end you have to find the workflow that fits to you/your team.

Personally, I can only recommend to use Git, even if you are a single developer. And I can’t imagine to go back to Subversion.

Anyway, give it a try, and don’t get discouraged by this article ;-)

After having gone through that ordeal I’m convinced that git just isn’t suited to individual development or small teams.

Yes, I’m using dreamhost. Though I don’t have any experience with webdav and multi-dev Git setups… Stupid question: couldn’t you just give everyone in your team ssh access, and the problem would disappear?

though, I won’t name the bare repo “bare” to avoid confusion ( maybe hub? central? or something meaningful ), but again this is only for a single dev so who cares.

hmm, are you on dreamhost ?

the reason I ask is that I have a domain I want to use to host repos for the internal team, and they don’t necessarly have ssh access.
so webdav wasn’t a choice. ended up working but since repo folder is no longer owned by the shell user, I can’t chmod +x post-update and thus the automation isn’t working.
I’ll see if I can install gitosis :/