[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Alternatives for remote access?

From: Scott Lenser <slenser_at_cs.cmu.edu>
Date: 2002-08-30 22:39:16 CEST

> Alan Shutko <ats@acm.org> writes:
> > 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.
> That's true. Our INSTALL document walks you through the simple
> process: build or install apache2, drop mod_dav_svn into place, and
> add a <Location> block to apache's config file. It's incredibly
> simple to do. We're treating apache as a generic server process.

I haven't looked in a while, but last time I did the INSTALL document
didn't include any instructions for how to setup encryption on the
communication channels. Setting up a basic web server is pretty easy,
but setting up a secure web server seems to be a lot more work (I can't
tell for sure since I've never successfully set one up). With CVS, I
don't have to worry about this since it will happily use ssh as the
transport mechanism (I need ssh installed anyway).

- Scott Lenser

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Aug 30 22:39:45 2002

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.