[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: "Complex" project tree through https

From: Blair Zajac <blair_at_orcaware.com>
Date: 2007-11-12 18:35:37 CET

Lluis wrote:
> Hello all,
>
> I'm currently trying to make all the group's projects available through
> https with apache+svn+ldap.
>
> The configuration is like this:
>
> svn:svn /home/projects
> svn:proj1 /home/projects/proj1
> svn:proj1 /home/projects/proj1/svn
> svn:proj1 /home/projects/proj1/public_html
>
> Both svn and proj1 have read&write permission on all the contents.
>
> I'm trying to make both directories svn and public_html for each project
> available through https://host/projects/<project> and
> https://host/svn/<project> with this:
>
> AliasMatch ^/projects/([a-zA-Z0-9]+)/?(.*) /home/projects/$1/public_html/$2
> <LocationMatch /svn/([a-zA-Z0-9]+)>
> DAV svn
> SVNPath /home/projects/$1/svn
> AuthType Basic
> AuthBasicProvider ldap
> AuthName "Repository Subversion"
> AuthLDAPURL "ldap://ldap/ou=People,dc=ldaphost?uid?one?(objectClass=posixAccount)"
> AuthzLDAPAuthoritative on
> Require valid-user
> </Locationmatch>
>
> What I've found on the internet is that it's not possible to use a
> backreference inside a LocationMatch, so... do you have any ideas of a
> workaround for this? (the public_html is working fine)
>
> What I'm trying to avoid is putting the project's public_html and
> subversion repository in different trees.

You can just remove the SVNPath part in the LocationMatch. However, you'll need
separate Location's for each svn or use the SVNParentPath so you can have only
one Location block.

Blair

-- 
Blair Zajac, Ph.D.
http://www.orcaware.com/svn/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Nov 12 18:36:12 2007

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.