Re: Alternatives for remote access?

Darryl Melander <djmelan@sandia.gov> writes:

> The first and biggest obstacle is that the members of my team don't have
> expertise in setting up a web server.

Don't think of it as setting up a web server. If there isn't
already, there will be a simple recipe for setting up a
single-purpose Apache for svn, running on a port of your choice.

There's no reason the Apache process has to be considered a web
server. It can be configured not to serve any content other than
SVN, with as much security as ssh has.

If your security policy is so strict as to prohibit you from using
any protocol other than ssh, you'd better hope that ra_pipe gets
finished. (I'm sure patches would be accepted!) Or you could
conceivably run an Apache/SVN on the machine with a port not open to
the outside, and use ssh port forwarding.

-- 
Alan Shutko <ats@acm.org> - In a variety of flavors!
Immortality for sale, Lifetime Guarantee!
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org