You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Jeff Mitchell <je...@gmail.com> on 2008/03/05 15:05:57 UTC
Questions about migrating from svnserve to Apache
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@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Questions about migrating from svnserve to Apache
Posted by Jeff Mitchell <je...@gmail.com>.
Thanks!
I did get a setup working with ViewVC and HTTP subversion...the ViewVC
URLs have /viewvc/ in them but that's it...you can hit up
http://server from both the svn client and a web browser. I didn't
figure out a way to have it use different virtual hosts and rewrite
rules based on the client. As promised, I'll post the info (in a
separate posting) in case it helps anyone in the future (and if anyone
can enhance it, great!)
--Jeff
On Fri, Mar 7, 2008 at 1:21 AM, Ryan Schmidt
<su...@ryandesign.com> wrote:
> On Mar 6, 2008, at 06:14, Jeff Mitchell wrote:
>
>
>
> > On Thu, Mar 6, 2008 at 1:39 AM, Ryan Schmidt wrote:
> >
> >> 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
> >> mod_dav_svn.
> >
> > Generally the ViewVC URLs are different only in that they contain
> > "/viewvc/" in them...I've already been thinking about ways I could get
> > around that, by changing around my ScriptAlias value. But your
> > mod_rewrite + vhosts idea seems doable...I'll give it a go and post
> > configuration here if I'm successful.
> >
> >> It is possible and is described here:
> >>
> >> http://svnbook.red-bean.com/en/1.4/svn.serverconfig.multimethod.html
> >
> > I saw this page but it only talks about Berkeley DB backends and
> > doesn't mention FSFS anywhere. It would make sense that it's doable
> > with a database, but I'm more concerned with how it handles it with
> > the filesystem repository. Do you know if this is supported with
> > FSFS?
>
> I believe it applies equally to FSFS repositories. I have requested
> clarification in the book:
>
> http://www.red-bean.com/pipermail/svnbook-dev/2008-March/003770.html
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Questions about migrating from svnserve to Apache
Posted by Ryan Schmidt <su...@ryandesign.com>.
On Mar 6, 2008, at 06:14, Jeff Mitchell wrote:
> On Thu, Mar 6, 2008 at 1:39 AM, Ryan Schmidt wrote:
>
>> 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
>> mod_dav_svn.
>
> Generally the ViewVC URLs are different only in that they contain
> "/viewvc/" in them...I've already been thinking about ways I could get
> around that, by changing around my ScriptAlias value. But your
> mod_rewrite + vhosts idea seems doable...I'll give it a go and post
> configuration here if I'm successful.
>
>> It is possible and is described here:
>>
>> http://svnbook.red-bean.com/en/1.4/svn.serverconfig.multimethod.html
>
> I saw this page but it only talks about Berkeley DB backends and
> doesn't mention FSFS anywhere. It would make sense that it's doable
> with a database, but I'm more concerned with how it handles it with
> the filesystem repository. Do you know if this is supported with
> FSFS?
I believe it applies equally to FSFS repositories. I have requested
clarification in the book:
http://www.red-bean.com/pipermail/svnbook-dev/2008-March/003770.html
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Questions about migrating from svnserve to Apache
Posted by Jeff Mitchell <je...@gmail.com>.
On Thu, Mar 6, 2008 at 1:39 AM, Ryan Schmidt
<su...@ryandesign.com> wrote:
> 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
> mod_dav_svn.
Generally the ViewVC URLs are different only in that they contain
"/viewvc/" in them...I've already been thinking about ways I could get
around that, by changing around my ScriptAlias value. But your
mod_rewrite + vhosts idea seems doable...I'll give it a go and post
configuration here if I'm successful.
> It is possible and is described here:
>
> http://svnbook.red-bean.com/en/1.4/svn.serverconfig.multimethod.html
I saw this page but it only talks about Berkeley DB backends and
doesn't mention FSFS anywhere. It would make sense that it's doable
with a database, but I'm more concerned with how it handles it with
the filesystem repository. Do you know if this is supported with
FSFS?
Thanks,
Jeff
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Questions about migrating from svnserve to Apache
Posted by Ryan Schmidt <su...@ryandesign.com>.
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
mod_dav_svn.
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:
http://svnbook.red-bean.com/en/1.4/svn.serverconfig.multimethod.html
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org