Sebastian Tennant wrote:
> Hi list,
>
> How to deploy svnserve securely _and_ provide local read/write access to
> a repository at the same time.
>
> _Feedback most welcome_.
Here's my feedback: don't do this! Local users don't need read/write
access to the repository (using file://) and in fact it is a bad idea to
give them access. file:// access is ideal for testing, but is not a
robust method for multiuser access; if you are thinking it is faster,
you should consider how long it would take you to recover a corrupt
repository or restore from backup as part of your considerations.
Just use a server process that owns the repository files exclusively and
have the local users access the repo exactly like the remote users - via
the server process. Whether you use svnserve or Apache, it is much more
robust and secure to have the repository unavailable via file:// completely.
My 2 cents
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-02-26 16:08:03 CET