Hosting from Windows XP.

Hello Everyone,

I'm trying to get git set up for my company. We're stuck using Windows for the foreseeable future so for now I have to host the central integration repository out of a Windows box. I figured the easiest way to do this, short of installing cygwin, would be to do a simple msysgit install and then run git daemon with the relevant repo copied over onto the server. Then devs could track that repo. However, it appears that msysgit does not install git daemon.

I may totally be missing something here, but I don't know what. Short of the question is, how do I host a repo out of Windows?

Thanks in advance!

Tim Visher <tim.visher@gmail.com> wrote:

git-daemon isn't ported yet, due to its heavy reliance on POSIX
behavior during fork+exec.
 

I think your options are limited to:

- Use Cygwin
- Use a virtual machine running Linux with git inside it
- Use JGit and its daemon

"Shawn O. Pearce" <spearce@spearce.org> writes:

You can use instead "dumb" HTTP protocol, or network filesystem (network share). Or SSH.

Note that for push you don't [usually] use git-daemon: you can use SSH, filesystem (network share), HTTPS with WebDAV.

[...]

packfiles, as it does not support delta compression yet...

Jakub Narebski <jnareb@gmail.com> wrote:

Yes.

It does however support delta-reuse, and it only supports the index-pack variant during receive-pack. So it saves and reuses any deltas created by C git. Which makes it almost tolerable to work with as a bit server.

Hi,

On Mon, 26 Jan 2009, Tim Visher wrote:

Use a net share. Use the native permission system to restrict/open up the repository for certain people to read from/write to.

Ciao, Dscho

Hi,

On Tue, Jan 27, 2009 at 12:45 AM, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:

hmm, does this entail git daemon usage too?

Tay Ray Chuan <rctay89@gmail.com> wrote:

No, developers would be accessing the repository directly over SMB.

Its slower than if you used git daemon. Access over SMB is tolerable, especially if your network is fast, but there's still a lot more data transfer then if the native git protocol could be used.

Hi,

On Tue, Jan 27, 2009 at 12:27 AM, Tim Visher <tim.visher@gmail.com> wrote:

you might want to look at using pushing over DAV: say, have all your employees pulling from a DAV-enabled server.

The DAV protocol itself is platform-agnostic, so your server could be Windows or Linux or whatever. Since DAV deals with file I/O, you might want to look at your security options, though I think basic access authentication would be enough if your server is only accessible within your company's LAN.

By pushing over DAV, you can avoid running a git daemon. Looking at how you would do this on Windows, i don't think it's advisable to do so.

To do this, first, you would need to have cygwin, then you have to run "cygrunsrv -I", which will install your git daemon as a Windows service.

AFAIK, cygrunsrv pipes stuff to git-daemon. I don't know how good this option is, reliablity or performance-wise.

I've tried this out (somewhat limitedly) using git built on cygwin, with an Apache server, though currently you would have problems if your Apache was running on a Windows box (my patch to fix this is on its way).

On 2009-01-26, Tim Visher <tim.visher@gmail.com> wrote:

I know you said "short of installing cygwin", but I'd like to ask you if you have ever used CygWin. I'd suggest you give it a try first (if you haven't already) because it would then enable you to use a wide range of tools from the unix-world without a lot of hassle. git, for example, can be downloaded and compiled out-of-the-box, meaning the git-daemon as well. You even get an ssh-server with cygwin (on windows, how cool is that ;).

Greetings, Jojo

Well, I ended up going with Cygwin. Didn't feel like the hassle of all of the rest of that stuff. Thanks so much, everyone. :)