Git or svn on windows server 2003
I was wondering if anyone has any experience on getting a git server working on windows server 2003? Is there an easy solution to get it up and running? If not is there any good alternatives out there?
It ideally has to be free but willing to pay. It is only for a small team (3 users) but we desperately need source control!
We need to host it on our windows server as this is where are sites/code is kept!
I have previous experience with git but not with setting up my own server so an point in the right direction would be great.
One Solution collect form web for “Git or svn on windows server 2003”
From my experience, the easiest way to get a Git server on a Windows machine is to run a virtual Linux server, and then use something like Gitolite. There’s GitStack which is a proprietary package that allows two users for free, but charges for more than that.
I’m more familiar with the Subversion servers for Windows. Maybe someone more familiar with Git can explain the Git on Windows server options.
Meanwhile, here are just a few of the Subversion on Windows options.:
- Subversion comes with
svnservewhich is a lightweight server that uses it’s own protocol. It’s fast and easy to install on Windows as a Windows service.
- Subversion comes with
- There are two well known GUI Windows Subversion servers out there: VisualSVN and UberSVN. Both of these are proprietary servers, but are free as long as you don’t use any advanced features (like tying your repository to LDAP). Both have GUI interfaces which make it quick and easy to setup.
- If you’re more of a brave sole, you can get the CollabNet’s Subversion Edge package which is entirely open source. It’s a bit more work, but it’s completely open source. CollabNet gives you an Apache httpd server that’s compiled to work as a Subversion server with all the required modules. Setup is a bit more complex than the others, but it’s not something a developer can’t easily do. The big advantage is that you can do things like integrate LDAP or Active Directory or use secure certificates (https), so your Subversion commits and updates aren’t sent plain text over the network without paying extra. Just be prepared to open the back and scout around for user serviceable parts.
Then again, you can share Git repositories back and forth with each other without even having a server. You can use things like email and Dropbox to share updates to the repository with each other. It’s one of the big advantages Git has have since it is a distributed version control system.