Last year I found myself in a sudden and quick need to set up working environment for a team of four, and as I like Git very much, I wanted to use it as our VCS. The problem was, we weren’t allowed to use any third party provider, so GitHub was off the table. As I searched the Internet there were a few guides to set up team Git environment on Windows, but they all seemed very complicated and time consuming. For our modest needs we experimented a little and came up with a solution that was very simple, didn’t require any additional software to be installed anywhere and worked like a charm.
Recently I used it again on my current engagement, and one of my colleagues suggested I should blog it, so here goes.
Ready, steady, go
The guide assumes you already have your local Git set up. For that, there are plenty of resources on the Internet, including my own blogpost about Windows Git tooling.
The entire tricks works like this – expose folder containing your shared Git repository as Windows network share.
Step one – bare git repository
There are two twists to the entire solution – one of them is – your shared repository needs to be initialized with –bare flag.
Step two – Windows share
Second step is to expose the folder with our newly created repository on the Windows share. You also use your standard Windows mechanisms to control and limit access to the folder (make sure you give the developers write access!).
Step three – Map the share as network drive
This step is perhaps not exactly necessary but I couldn’t get it to work otherwise, so here comes the second twist. In order for your developers to be able to access the shared folder via Git they need to map it as network drive.
Step four – Add remote repository in Git and code away
Last step is the standard Git procedure – every developer on your team needs to add the repository sitting under their newly created network drive as remote. Notice the use of “file:///” prefix in front of the mapped drive name.
That’s all. I hope you find it useful, and if you know a way to eliminate step three, let me know in the comments.
Last time we solve same problem we end up using simple web-site based solutions like Bonobo or GitAspx. This will eliminate step 3 🙂
the mapping network drive step could be skipped, by using
git remote add shared //yourserver/sharepath/sharename