Eric Radman wrote:
> On 02:06 Sat 26 Feb , Ian Bicking wrote:
>
>>Eric Radman wrote:
>>
>>>We can keep one big "global" database, but then user's can't be
>>>authenticated against specific relms, and very few need access to Home.
>>>The password file for all three is /etc/subversion/passwd. Is this
>>>correct?
>>
>>No, /etc/apache2/dav_svn.passwd.
>
>
> I checked out the backup I made of repository; svnserve.conf is using
> /etc/subversion/passwd, which is a clear text file. Are we talking about
> two different things? As far as I can tell dav_svn.passwd won't work for
> svn:// authentication.
That is true, but I'd like to make the svn: interface obsolete, since we
can't control the permissions. I don't know of an easy way to keep
those in sync either. It just means we don't add user accounts to
/etc/subversion/passwd, we only add them to /etc/apache2/dav_svn.passwd
>>Or something close to that. For the most part I don't see any reason to
>>keep the repositories separate.
>
>
> It doesn't matter that much to me, so I merged them together so the root
> path works:
>
> http://svn.webwareforpython.org/
>
> I only kept the revision history on /Webware. All of the backups are in
> my home folder under svn-backups.
What happened to everything that was in the repository before, like
Component and Wiki...? I think the repository needs to be restored from
backup and Webware CVS merged in again; I don't want to lose all that
history, and there's no real reason to.
Also, anyone should feel free to branch any part of the repository,
regardless of permission, and that's easier to arrange when it's just
one repository.
--
Ian Bicking / ianb@... / http://blog.ianbicking.org
|