On 2/26/07, tien vuong <vuongtuyettien@yahoo.com> wrote:
> Hello list members,
>
> I am using TortoiseSVN-1.3.0.5301-RC1, and
> svnserve-1.2.3 to serve remote clients.
>
> Since
> "svnserve only understands "blanket" access control. A
> user either has universal read/write access, universal
> read access, or no access. There is no detailed
> control over access to specific paths within the
> repository."
> (http://svnbook.red-bean.com/en/1.1/ch06s03.html)
>
> I used to run 2 instances of svnserver (each listens
> at a different port) to allow remote accessing to 2
> different repositories with different user access
> permissions on each.
>
> There has been inconvenience to run a svnserve
> listening at a port different from the default port.
> But I didn't know a better way.
>
> Recently, I did an almost insane trial. Unexpectedly,
> the trial showed that one svnserve can serve more than
> one repository with different user accounts for each.
>
> /repos
> /conf
> /dav
> /db
> /hooks
> /locks
> /repos_1
> /conf
> ...
> /repos_2
> /conf
> ...
>
> First, I create an repository at /repos, leave its
> configuration as default. Under /repos, I create 2
> folders /repos_1 and /repos_2. I create 2 new
> repositories at /repos_1 and /repos_2 and these 2
> places are where my 2 different sources are really
> imported. repos_1 and repos_2 have different user
> lists configured in their passwd and svnserve.conf
> files. svnserver root path is now pointed to /repos
> (svnserver -d -r C:\repos).
>
> Surprisingly, from a remote PC, I can access
> svn:\\[serverhost]\repos_1
> and
> svn:\\[serverhost]\repos_2
> with different accounts registered for each
> repository.
>
> Though it seems wrong to create a repository within
> another repository location, what I can see is it is
> not more a problem than having one un-used repository
> (/repos).
>
> Has somebody tried that? Is it wrong or is there any
> bad side-effect?
>
> Tien
I haven't done it this way, but I have multiple repositories being
serviced by a single svnserve process. I have a directory
(/ct/ctsvn/repositories) in which I create the different repositories
that will be handled by the svnserve daemon. So,
/ct/ctsvn/repositories/repos1, /ct/ctsvn/repositories/repos2, etc,
each with their own subdirs (conf, db, etc).
Then, start svnserve in daemon mode as you were, passing the directory
in which it will find the various repositories (svnserve -d -r
/ct/ctsvn/repositories).
This has worked for me just fine, since we've started using
Subversion. It looks a bit cleaner than what you suggested, as each
repository maintains its own files (there would be no difference if
you decided you wanted to use different svnserve processes later on..)
Hope this helps,
Ed
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Mon Feb 26 23:01:34 2007