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

Questions about migrating from svnserve to Apache

From: Jeff Mitchell <jeffrey.mitchell_at_gmail.com>
Date: Wed, 5 Mar 2008 10:05:57 -0500

Hello,

We're considering migrating from svnserve to Apache. The main reason
is that we have NIS set up, but when we started using Subversion we
didn't have a way to integrate it with Apache (were running Apache
1.3) so we had to go the svnserve route. But we'd like to make things
integrated so people have more of a "single sign on" to both computers
and Subversion.

There are two concerns/questions I have though.

The first is that our Apache server is serving ViewVC out of the root
of the server, for instance http://svn. We'd really like to keep it
that way; ViewVC is excellent and we prefer it over the built-in
browsing. In the Subversion Book, it says to make sure that your
<Location> directive doesn't overlap your <DocumentRoot>. I'm
wondering if this means that Apache can tell what kind of request is
coming in and delegate to mod_dav_svn or not, so that people can still
go to http://svn in a web browser and get ViewVC, or people can do a
"svn co http://svn/blah" and get the proper Subversion handling. Is
that true, or is there some way to make this possible?

The other question is, to ease migration, we were hoping that you
could have the same repository served by two subversion servers --
i.e. Apache with mod_dav_svn and svnserve at the same time. That way
people could gradually migrate to Apache without having to have a
sudden cutoff. Is this possible, or are we looking at corruption if
we try it? We're using FSFS.

Thanks,
Jeff

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-03-05 16:06:38 CET

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

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