The simple trick to user rights I use is to make the repo owned by www-data to give Apache access and use group permissions for svn+SSH. I'm not sure if acl's work or not.
I always viewed svn as just being a method to interact with individual repos... it really has no clue what is going on outside of its own world. To handle this issue, I made a wrapper script for svnadmin that parses the input and output and logs to an SQL database which I then access through Apache to build a display list of repos (and change logs).
Matt
----------------------------------------
Matthew Beals
Michigan Technological University
Department of Atmospheric Sciences
1400 Townsend Drive
B019a Fisher Hall
Houghton, MI 49931
mjbeals_at_mtu.edu
Nico Kadel-Garcia <nkadel_at_gmail.com> wrote:
On Mon, Jul 18, 2011 at 4:56 AM, Andy Canfield <andy.canfield_at_pimco.mobi> wrote:
>
>
> On 07/18/2011 09:36 AM, Nico Kadel-Garcia wrote:
>>
>> On Sun, Jul 17, 2011 at 8:07 AM, Andy Levy<andy.levy_at_gmail.com> wrote:
>>>
>>> On Sun, Jul 17, 2011 at 02:06, Andy Canfield<andy.canfield_at_pimco.mobi>
>>> wrote:
>>>>
>>>> How do you get a list of repositories from svnserver? The only way I can
>>>> figure out is:
>>>> ssh username_at_example.com
>>>> sudo bash
>>>> ls -ld /var/svn/*
>>>> And, of course, this makes an assumption about where on the server the
>>>> repositories are located. There 'ought' to be an easier way.
>>>
>>> There is, but only if you serve via Apache.
>>
>> Even then, it won't find repositories that are not built into the
>> Apache layout or the elevant "parent" directory.
>
> I would think that it looks at SVNParentPath and tries to treat every
> subdirectory of that as a repository.
Not quite. It's not "every subdirectory", it's "every child
directory". That means it will not descend into subdirectories of
subdirectories, fir example, so they all need to be right there in
/var/svn. Also, while symlinks to other locations may be acceptable to
the mod_dav_svn module, the repositories need to be accessible to the
"apache" user. This can get adventuresome if you're running svnserve
or svn+ssh access without a devault svn+ssh user, used in parallel to
Apache.
Received on 2011-07-18 13:48:37 CEST