Windows Server?

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.
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?

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)?

--John
(watch out for the footer...)

TradeStation 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.
  If you received this in error, please contact the sender and delete the material from any computer.

2009/4/28 John Dlugosz [off-list ref]:

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

John Dlugosz [off-list ref] wrote:

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.

Yea, really, you want a Git server of some kind on that host.
file:// over SMB over VPN isn't pretty.
 

I suppose that git-daemon isn't available as a Windows service.

Nope.  You could try JGit and its "jgit daemon".  Its a pure
Java server.

I
posted a short time ago asking about it, and the news did not seem good.
So, is ssh a good second?

How are you going to run SSH on the server?  Cygwin SSH?

But yes, the SSH protocol is the git:// protocol, tunneled through SSH,
and will be much more efficient over the VPN than SMB.

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, not really.
 
-- 
Shawn.

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.

Ah, good to know.  Thanks.

Yes, using ssh is fine.

quoted

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?

I suppose it also needs to have the main git executable on the system
PATH or be set up as some kind of alias known by the ssh server.  I
suppose it works by launching a shell on the server's end and feeding it
the command from the client's side.

I use PUtty at home for a shell into my Debian server.  I don't know how
git invokes it, but it's obviously other than having a GUI application
create a window for that purpose.  I'll dive into enabling/configuring
that once I have the server end going.

--John


TradeStation 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.
  If you received this in error, please contact the sender and delete the material from any computer.

How are you going to run SSH on the server?  Cygwin SSH?

My first idea is to let the I.T. guys figure that out.  After all, they
are supposed to be helping us...right?  Is such a thing built into a
Windows server system?  But a quick search in Google turned up a
SourceForge project that's OpenSSH using a stripped down Cygwin that is
self-contained and doesn't require a separate Cygwin installation.

But yes, the SSH protocol is the git:// protocol, tunneled through

SSH,

and will be much more efficient over the VPN than SMB.

Someone else said that the git daemon is for fetching only.  So that's
not a limitation with the git: protocol, just the git-daemon itself?


--John

TradeStation 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.
  If you received this in error, please contact the sender and delete the material from any computer.

John Dlugosz [off-list ref] wrote:

quoted

But yes, the SSH protocol is the git:// protocol, tunneled through

SSH,

quoted

and will be much more efficient over the VPN than SMB.

Someone else said that the git daemon is for fetching only.  So that's
not a limitation with the git: protocol, just the git-daemon itself?

Correct.  Actually, git-daemon can support pushing.  Its just that
it has *no* authentication, so enabling push support on the daemon
is really risky as anyone who has network access to the server can
update the repositories it hosts.

-- 
Shawn.