I can only answer part of this question, as I have only used msysgit with myself, and occasionally over SMBFS. (Every time I do so, I cross my fingers and hope it works. So far it has.)
On Tue, Apr 29, 2008 at 12:18 AM, Sitaram Chamarty <[EMAIL PROTECTED]> wrote: > > Hello, > > I saw some messages about git daemon in the list when I searched, but > of course the 1.5.5. version (...20080413.exe) doesn't have the > command. > > For someone who does not have the windows smarts to compile mingw and > all that, what options do I have to get a minimal git daemon working? > Where can I download a "daily trunk build" sort of thing and would > that be a bit of a problem to use with production code? > > On a more generic level, is there a good source of information on > getting a git setup going for a group of people using windows? My > biggest problem is getting them to even pull from each other (never > mind push!) > > Git daemon doesn't exist so git-daemon doesn't work. I can't find an > ssh server for windows -- the only one that claims to be a server (at > http://sshwindows.sourceforge.net/ ) says you can't use it if you have > cygwin, and I'm not sure if mingw counts as having cygwin. (I'm still > trying to figure out why that server didn't work, meanwhile). Doing > pulls over HTTP seems painful and suboptimal, plus it requires > lighttpd or apache -- I'm trying to get something lightweight going > here!. MinGW and Cygwin are definitely *not* the same thing. They both provide POSIX compatibility for Windows. But they have different philosophies. Cygwin (at least in its default configurations) is a relatively heavy environment that lives on your PC. I believe just about every program compiled for Cygwin runs against cygwin.dll. MinGW programs are more self-contained, typically do not require external DLLs (varies according to the application, of course), and therefore can be run from a plain Windows command prompt. (I prefer to use Git bash, just because it's much more capable than a Windows command prompt.) Therefore the prohibition against using SSHWindows with Cygwin shouldn't apply to msysgit. But I haven't tried it. Depending on your tolerance for using seemingly arcane utilities, setting up an SSH server on Windows might be slightly intimidating, or not that bad, what with generating keys for the server and for each user. I have found that the "Putty" SSH programs make life much easier in this regard. http://www.chiark.greenend.org.uk/~sgtatham/putty/ I found that this guide on how to use Putty, SSH, and Git -- while not written specifically for msysgit -- was sufficiently user friendly for a person such as myself who didn't want to become a professional SSH administrator. ;) Link here: http://github.com/guides/providing-your-ssh-key I have to say that the boys (and girls?) on Msysgit have done a fine job recent versions of the installer. The past few builds I've been able to point-and-click install on a few machines painlessly. > > My next 2 options are (1) make everyone use shared folders mapped to > G: or something and clone/push/pull from there, even though the main > git FAQ says SMBFS is not advisable, or (2) go for the full cygwin > experience, openssh and all... Perhaps you *could* just use Github. There are other public, private, free, and commercial Git hosting services cropping up all over now. I have no experience with these, either. (For instance, supposedly Unfuddle.com is supposed to have Git hosting on May 15. http://www.pbell.com/index.cfm/2008/4/25/The-Rise-of-Git-for-Version-Control) > > > Any thoughts and ideas will be most appreciated. Pointers to other > places where someone's done it all before are also welcome :-) > > Thanks and regards, > > Sitaram >
