> -----Original Message----- > From: Chris Rodgers [mailto:christopher.rodg...@cardiov.ox.ac.uk] > Sent: 22 October 2013 16:51 > > > ...but what should be there? If you want a list of > > repositories then I would suggest investigating the > > `SVNParentPath` directive. > > 1/ If you comment out the alias directive, does you svn work ok? > > 2/ what are you trying to serve via the `/repos` URL? > > > > ~ Mark C > > > > Hi Mark, > > 1) Yes, SVN does then work OK. > > But I then get a 404 error from https://server/repos/
What is in /srv/svn/repos/thereponame? SVNPath should point to a single repository root folder (the one with the conf, dav, db etc folders. > 2) I am using the http://www.reposstyle.com/ style sheet, so each > repository root has an "Up" button in the HTML page that is > served... I > wanted a blank directory listing with a quick ".." link for > getting back > to the server root. The intention was not to reveal the repos names > whilst avoiding the dead link from the repo root folder. I am not sure I understand. Do you want to use `SVNParentPath` to serve a group of repositories without actually revealing the list of repo names? You should be able to do that be editing the style sheet to not list the actual names but then how are your users going to find their repos? > I still don't really understand the need for this warning: > > There is no folder "thereponame" in /srv/svn/html so nothing actually > conflicts. It does because the alias is matched first and affects your loaction directive (I could well be wrong but I cannot see how to use the two together without potential issues). Can I suggest: instead of asking for a solution to your specific problem, ask how to achieve what you actually want (i.e. describe if my guess above is wrong)... ~ Mark C > If I removed the Alias, wouldn't there still be a > potential-but-not-in-fact conflict between a path on disk > /htdocs/repos/thereponame (which doesn't exist) and the > repository URL > https://server/repos/thereponame/ ?? > > C. >
