On Mar 5, 2008, at 09:05, Jeff Mitchell wrote:
> 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?
I've thought about building a web repo viewer which would use URLs
identical to mod_dav_svn but provide more info. I played around with
ways of configuring apache to direct regular web browsers to this
view but a Subversion client to mod_dav_svn. I think it can be done.
The advantage is that you could copy a URL from the web browser and
paste it into a Subversion client. But I don't think I'd recommend it
for ViewVC whose URLs don't, I think, match mod_dav_svn's. I'd
recommend two different vhosts: "viewvc" for viewvc, "svn" for
You could probably install a simple mod_rewrite rule on the "svn"
vhost to redirect non-svn user agents to the "viewvc" vhost, to
support users still using the "svn" vhost in a web browser expecting
to get to your viewvc. That may be as simple as checking if the
useragent contains the string "svn" but you should look at a few
different Subversion clients' useragent strings to see what they use.
> 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.
It is possible and is described here:
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-06 07:40:04 CET