2009/4/28 John Dlugosz <JDlugosz@xxxxxxxxxxxxxxxx>: > We are a Windows' shop, writing software that runs on Windows. > Naturally, the network location I.T. provided for the repository is on a > Windows server. I'm concerned with using file:// access once everyone > starts using it in earnest, especially over a cross-continent VPN. > > I suppose that git-daemon isn't available as a Windows service. I > posted a short time ago asking about it, and the news did not seem good. Well, git-daemon speaks the git:// protocol which generally is for pull only. If you're wanting push and pull access, using something like ssh is the way to go. > So, is ssh a good second? That is, the manipulations of the central > repo is being done by the machine that owns that disk, and the protocol > talks between the two copies of git? Yes, using ssh is fine. > Is there anything that needs to be done on the server machine, other > than having a SSH server, and formulating the path the way the disk > really is on that machine (as opposed to the network share structure)? Nope -- a running ssh server is all that's needed. The clients then would need an ssh-client to contact the server over ssh, of course. Not knowing anything about WIndows, would putty provide this? -- Thomas Adam -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html