Marko Käning wrote:
> What I in fact only gain is ISOLATION of my repos from direct access due
> to many ssh users on a file-basis. Instead only svnserve accesses the
> repos.
Correct, except that last bit is also true of running svnserve as a
server. In both the Apache server and svnserve (as server) cases, the
repository is accessed by a single account. You can also accomplish
that using the svn+ssh with a shared authorized_keys file, but you don't
have to do it that way.
> Still there can be many users accessing the repos at a time, but that will
> spawn also many svnserve processes which will handle the access to the
> repos in a much safer way.
All multiprocess repository access is handled in a safe manner, whether
you are using Apache, svnserve, local (i.e. file://) access or in fact
all of the above. Don't get distracted by this point; Subversion was
written to be multi-process (e.g. threadsafe) from the very beginning.
What you really need to focus on is:
1) How many users will be accessing the repository total?
2) How many users will be accessing the repository at a single time?
3) How much infrastructure do you want to maintain to handle both
authentication and authorization?
There isn't One True Answer(TM) to these questions. With a small group
of slowly changing users who have complete access to the entire
repository, svn+ssh:// is a perfectly acceptable solution. However, a
large number of users, with a high turnover rate, who each need rights
to only a small portion of the total repository, svn+ssh:// will not
work for you and Apache would be much easier to manage. Only you can
make those determinations...
John
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-07-29 15:52:16 CEST