Hi Ryan,
Thanks for the info.
I am running svnserve for client access through TortoiseSVN. This is for
users who wants to checkout and checkin the code.
There are some users who just want to browse the code in Internet Explorer.
The http in browser is required for users who browse code without checkout
using TortoiseSVN client. How to achieve this.
So, I have installed svn using configure.sh script i have used the serf
library path. But serf is not serving the http for svn repository. So my
doubt is whether the following option will provide http support when svn is
installed with below options.
I hope this explains what my requirement is.
--with-apxs[=FILE] Build shared Apache modules. FILE is the optional
pathname to the Apache apxs tool; defaults to
"apxs".
--with-apache-libexecdir[=PATH]
Install Apache modules to Apache's configured
modules directory instead of LIBEXECDIR; if PATH
is
given, install to PATH.
regards,
Arun
On Fri, Dec 18, 2015 at 12:04 AM, Ryan Schmidt <
subversion-2015_at_ryandesign.com> wrote:
>
> On Dec 17, 2015, at 8:09 AM, arun prasath wrote:
>
> > I have situation which needs your suggestion and help in setting up the
> svn1.9.2 with svnserve + http access in browser. My below talks about my
> svn setup.
> > SVN working method:
> > After installation, the svn://servername/reponame is working. But
> http://servername/reponame is not working and give the HTTP 404 error.
> >
> > Problem Description:
> > Am i missing something. I know Svn Apache modules are required for http
> access but i am running svnserve for client access and no Apache httpd is
> installed. For http access i have installed Serf library.
> >
> > Expected :
> > - What are required for running svn1.9.2 as svnserve daemon (with http
> support in browser)
> > -Is just serf library is not enough to serve http through svnserve
> > -how to pass the httpd modules to during subversion install
>
> Apache + mod_dav_svn is required to serve a Subversion repository over
> http (or https). You can run this simultaneously with svnserve for serving
> the repository over the svn protocol, provided you set up
> permissions/ownership properly. There's documentation in the book. However,
> I'm not sure what benefit there is to offering multiple access methods. For
> example, if you want to serve the repository over http via Apache +
> mod_dav_svn, then why also run svnserve?
>
> serf is the library the svn client uses to access a repository that is
> being served by Apache + mod_dav_svn.
>
>
>
Received on 2015-12-18 08:33:50 CET