git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: John Dlugosz <JDlugosz@TradeStation.com>
Cc: git@vger.kernel.org
Subject: Re: Windows Server?
Date: Tue, 28 Apr 2009 15:46:53 -0700	[thread overview]
Message-ID: <20090428224653.GT23604@spearce.org> (raw)
In-Reply-To: <450196A1AAAE4B42A00A8B27A59278E70AE3F0A6@EXCHANGE.trad.tradestation.com>

John Dlugosz <JDlugosz@TradeStation.com> 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.

  parent reply	other threads:[~2009-04-28 22:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-28 22:41 Windows Server? John Dlugosz
2009-04-28 22:46 ` Thomas Adam
2009-04-29 15:18   ` John Dlugosz
2009-04-28 22:46 ` Shawn O. Pearce [this message]
2009-04-29 15:22   ` John Dlugosz
2009-04-29 15:24     ` Shawn O. Pearce

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090428224653.GT23604@spearce.org \
    --to=spearce@spearce.org \
    --cc=JDlugosz@TradeStation.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).