{"thread":{"id":"19114","subject":"Windows Server?","startedAt":"2009-04-28T22:41:51Z","lastAt":"2009-04-29T15:24:37Z","messageCount":6,"participants":["John Dlugosz","Thomas Adam","Shawn O. Pearce"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"112570","messageId":"450196A1AAAE4B42A00A8B27A59278E70AE3F0A6@EXCHANGE.trad.tradestation.com","threadId":"19114","inReplyTo":null,"subject":"Windows Server?","fromName":"John Dlugosz","fromEmail":"jdlugosz@tradestation.com","sentAt":"2009-04-28T22:41:51Z","receivedAt":"2009-04-28T22:41:51Z","isPatch":false,"sender":{"key":"jdlugosz@tradestation.com","avatar":null},"body":"We are a Windows' shop, writing software that runs on Windows.\nNaturally, the network location I.T. provided for the repository is on a\nWindows server. I'm concerned with using file:// access once everyone\nstarts using it in earnest, especially over a cross-continent VPN.\n\nI suppose that git-daemon isn't available as a Windows service. I\nposted a short time ago asking about it, and the news did not seem good.\nSo, is ssh a good second? That is, the manipulations of the central\nrepo is being done by the machine that owns that disk, and the protocol\ntalks between the two copies of git?\n\nIs there anything that needs to be done on the server machine, other\nthan having a SSH server, and formulating the path the way the disk\nreally is on that machine (as opposed to the network share structure)?\n\n--John\n(watch out for the footer...)\n\nTradeStation Group, Inc. is a publicly-traded holding company (NASDAQ GS: TRAD) of three operating subsidiaries, TradeStation Securities, Inc. (Member NYSE, FINRA, SIPC and NFA), TradeStation Technologies, Inc., a trading software and subscription company, and TradeStation Europe Limited, a United Kingdom, FSA-authorized introducing brokerage firm. None of these companies provides trading or investment advice, recommendations or endorsements of any kind. The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited.\n If you received this in error, please contact the sender and delete the material from any computer.\n"},{"id":"112571","messageId":"18071eea0904281546u52423fe3saf7abaa486bfa0ec@mail.gmail.com","threadId":"19114","inReplyTo":"450196A1AAAE4B42A00A8B27A59278E70AE3F0A6@EXCHANGE.trad.tradestation.com","subject":"Re: Windows Server?","fromName":"Thomas Adam","fromEmail":"thomas.adam22@gmail.com","sentAt":"2009-04-28T22:46:00Z","receivedAt":"2009-04-28T22:46:00Z","isPatch":false,"sender":{"key":"thomas.adam22@gmail.com","avatar":"https://gravatar.com/avatar/137f9858bc6bfd5b2f743aefd988c81ce0cbd306248889df80e269519cfc8741?d=mp&s=160"},"body":"2009/4/28 John Dlugosz :\n> We are a Windows' shop, writing software that runs on Windows.\n> Naturally, the network location I.T. provided for the repository is on a\n> Windows server.  I'm concerned with using file:// access once everyone\n> starts using it in earnest, especially over a cross-continent VPN.\n>\n> I suppose that git-daemon isn't available as a Windows service.  I\n> posted a short time ago asking about it, and the news did not seem good.\n\nWell, git-daemon speaks the git:// protocol which generally is for\npull only. If you're wanting push and pull access, using something\nlike ssh is the way to go.\n\n> So, is ssh a good second?  That is, the manipulations of the central\n> repo is being done by the machine that owns that disk, and the protocol\n> talks between the two copies of git?\n\nYes, using ssh is fine.\n\n> Is there anything that needs to be done on the server machine, other\n> than having a SSH server, and formulating the path the way the disk\n> really is on that machine (as opposed to the network share structure)?\n\nNope -- a running ssh server is all that's needed. The clients then\nwould need an ssh-client to contact the server over ssh, of course.\nNot knowing anything about WIndows, would putty provide this?\n\n-- Thomas Adam\n"},{"id":"112572","messageId":"20090428224653.GT23604@spearce.org","threadId":"19114","inReplyTo":"450196A1AAAE4B42A00A8B27A59278E70AE3F0A6@EXCHANGE.trad.tradestation.com","subject":"Re: Windows Server?","fromName":"Shawn O. Pearce","fromEmail":"spearce@spearce.org","sentAt":"2009-04-28T22:46:53Z","receivedAt":"2009-04-28T22:46:53Z","isPatch":false,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"John Dlugosz wrote:\n> We are a Windows' shop, writing software that runs on Windows.\n> Naturally, the network location I.T. provided for the repository is on a\n> Windows server. I'm concerned with using file:// access once everyone\n> starts using it in earnest, especially over a cross-continent VPN.\n\nYea, really, you want a Git server of some kind on that host.\nfile:// over SMB over VPN isn't pretty.\n \n> I suppose that git-daemon isn't available as a Windows service.\n\nNope. You could try JGit and its \"jgit daemon\". Its a pure\nJava server.\n\n> I\n> posted a short time ago asking about it, and the news did not seem good.\n> So, is ssh a good second?\n\nHow are you going to run SSH on the server? Cygwin SSH?\n\nBut yes, the SSH protocol is the git:// protocol, tunneled through SSH,\nand will be much more efficient over the VPN than SMB.\n\n> Is there anything that needs to be done on the server machine, other\n> than having a SSH server, and formulating the path the way the disk\n> really is on that machine (as opposed to the network share structure)?\n\nNope, not really.\n \n-- \nShawn.\n"},{"id":"112641","messageId":"450196A1AAAE4B42A00A8B27A59278E70AE3F277@EXCHANGE.trad.tradestation.com","threadId":"19114","inReplyTo":"18071eea0904281546u52423fe3saf7abaa486bfa0ec@mail.gmail.com","subject":"RE: Windows Server?","fromName":"John Dlugosz","fromEmail":"jdlugosz@tradestation.com","sentAt":"2009-04-29T15:18:13Z","receivedAt":"2009-04-29T15:18:13Z","isPatch":false,"sender":{"key":"jdlugosz@tradestation.com","avatar":null},"body":"> Well, git-daemon speaks the git:// protocol which generally is for\n> pull only. If you're wanting push and pull access, using something\n> like ssh is the way to go.\n\nAh, good to know. Thanks.\n\n> \n> Yes, using ssh is fine.\n> \n> > Is there anything that needs to be done on the server machine, other\n> > than having a SSH server, and formulating the path the way the disk\n> > really is on that machine (as opposed to the network share\n> structure)?\n> \n> Nope -- a running ssh server is all that's needed. The clients then\n> would need an ssh-client to contact the server over ssh, of course.\n> Not knowing anything about WIndows, would putty provide this?\n\nI suppose it also needs to have the main git executable on the system\nPATH or be set up as some kind of alias known by the ssh server. I\nsuppose it works by launching a shell on the server's end and feeding it\nthe command from the client's side.\n\nI use PUtty at home for a shell into my Debian server. I don't know how\ngit invokes it, but it's obviously other than having a GUI application\ncreate a window for that purpose. I'll dive into enabling/configuring\nthat once I have the server end going.\n\n--John\n\n\nTradeStation Group, Inc. is a publicly-traded holding company (NASDAQ GS: TRAD) of three operating subsidiaries, TradeStation Securities, Inc. (Member NYSE, FINRA, SIPC and NFA), TradeStation Technologies, Inc., a trading software and subscription company, and TradeStation Europe Limited, a United Kingdom, FSA-authorized introducing brokerage firm. None of these companies provides trading or investment advice, recommendations or endorsements of any kind. The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited.\n If you received this in error, please contact the sender and delete the material from any computer.\n"},{"id":"112642","messageId":"450196A1AAAE4B42A00A8B27A59278E70AE3F27E@EXCHANGE.trad.tradestation.com","threadId":"19114","inReplyTo":"20090428224653.GT23604@spearce.org","subject":"RE: Windows Server?","fromName":"John Dlugosz","fromEmail":"jdlugosz@tradestation.com","sentAt":"2009-04-29T15:22:06Z","receivedAt":"2009-04-29T15:22:06Z","isPatch":false,"sender":{"key":"jdlugosz@tradestation.com","avatar":null},"body":"> How are you going to run SSH on the server? Cygwin SSH?\n\nMy first idea is to let the I.T. guys figure that out. After all, they\nare supposed to be helping us...right? Is such a thing built into a\nWindows server system? But a quick search in Google turned up a\nSourceForge project that's OpenSSH using a stripped down Cygwin that is\nself-contained and doesn't require a separate Cygwin installation.\n\n> But yes, the SSH protocol is the git:// protocol, tunneled through\nSSH,\n> and will be much more efficient over the VPN than SMB.\n\nSomeone else said that the git daemon is for fetching only. So that's\nnot a limitation with the git: protocol, just the git-daemon itself?\n\n\n--John\n\nTradeStation Group, Inc. is a publicly-traded holding company (NASDAQ GS: TRAD) of three operating subsidiaries, TradeStation Securities, Inc. (Member NYSE, FINRA, SIPC and NFA), TradeStation Technologies, Inc., a trading software and subscription company, and TradeStation Europe Limited, a United Kingdom, FSA-authorized introducing brokerage firm. None of these companies provides trading or investment advice, recommendations or endorsements of any kind. The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited.\n If you received this in error, please contact the sender and delete the material from any computer.\n"},{"id":"112643","messageId":"20090429152437.GC23604@spearce.org","threadId":"19114","inReplyTo":"450196A1AAAE4B42A00A8B27A59278E70AE3F27E@EXCHANGE.trad.tradestation.com","subject":"Re: Windows Server?","fromName":"Shawn O. Pearce","fromEmail":"spearce@spearce.org","sentAt":"2009-04-29T15:24:37Z","receivedAt":"2009-04-29T15:24:37Z","isPatch":false,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"John Dlugosz wrote:\n> > But yes, the SSH protocol is the git:// protocol, tunneled through\n> SSH,\n> > and will be much more efficient over the VPN than SMB.\n> \n> Someone else said that the git daemon is for fetching only. So that's\n> not a limitation with the git: protocol, just the git-daemon itself?\n\nCorrect. Actually, git-daemon can support pushing. Its just that\nit has *no* authentication, so enabling push support on the daemon\nis really risky as anyone who has network access to the server can\nupdate the repositories it hosts.\n\n-- \nShawn.\n"}]}