On Friday 07 March 2008, Shad Sharma wrote:
> >
> > The user running the apache must have r/w access to the directory on the
> > filesystem.
> >
> > Your repository seems to be located
> > in /home/cpnadmin/cargopartnersnetwork.com/repos/ but the path of the
> > virtual host is /home/cpnadmin/cargopartnersnetwork.com/html/ and there.
> > There is no Alias for this. That meens Apache looks up your repository
> > in /home/cpnadmin/cargopartnersnetwork.com/html/svn/ but it isn't really
> > there.
> >
> > Bernhard
>
> Hi Bernhard,
>
> That's an insightful point which I did explore, however, you are not
> supposed to create an alias to your svn folder from your html folder.
> If you do that, then apache tries to read that folder like a standard
> html folder instead of the special DAV svn type as instructed by the
> <Location> directive.
>
> I tried creating my repository in the actual html folder, i.e. at:
> /home/cpnadmin/cargopartnersnetwork.com/html/svn
> But this created new problems. The manuals I have been following
> mentioned nothing about being required to put the svn repository in
> the html folder (I tried it out of desperation).
>
> Currently, I am able to checkout existing projects with the current
> settings. This indicates that at least the read permissions are
> correct and the http GET requests are being handled correctly. In
> fact, I can even create folders in the repository. So, the write
> permissions are set correctly. This leads me to believe that there
> *must* be some strange directive in my apache configuration file that
> is somehow redirecting my request to the wrong directory, or a
> directive that is blocking the instruction based on a filter of some
> sorts. Unfortunately, I'm not sufficiently adept at reading the apache
> configuration to file to be able to tell which it is, if it is indeed
> one of these.
>
> Any other thoughts?
>
> Kind regards,
> Shad
Well, maybe you have some allow,deny directives in your httpd.conf or maybe
there's some superior <location> or <directory> directive which forbids
something you'd need in your svn-location.
It's hard to guess what may be wrong but if you post your httpd.conf I
propably can figure out the misconfiguration.
It cannot be a big mistake because usually is really easy to configure
Apache+SVN.
Bernhard
Received on 2008-03-07 10:15:55 CET