On Wed, May 21, 2008 at 1:29 PM, s1ntax <etheriad_at_gmail.com> wrote:
> Really? Could you provide sources that describe the pitfalls of using
> a shared file:// to help me create an intelligent proposal to my
> employer.
With file:// access, if you have access to the repository, you can
corrupt or delete it with one errant keystroke. There are known issues
with some network filesharing protocols which can cause corruption.
You have zero security - everyone can see and change anything in the
repository. You have no way to enforce standardized usernames (as
you've seen). Hook scripts execute local to the user who's performing
the action, not on the server itself.
http://subversion.tigris.org/faq.html#reposperms
Unfortunately I'm having difficulty locating anything that
authoritatively lists all the potential issues, but the short version
is: file:// access is intended only for single-user, local/testing
usage only. Multi-user environments should use a Subversion server
(svnserve or Apache) for safety - both in terms of security and
authorization.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-05-21 19:48:57 CEST