[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: SVN best practice: organising the SVN vault and organising your project

From: TM <tm_at_tm.uklinux.net>
Date: 2007-04-13 11:05:55 CEST

Hi Ryan,

I understand the potential pitfalls with using the 'file:' method to
access a vault on the intranet. The idea is that it's just a temporary
measure so that I am able to introduce Subversion to a (very) limited
number of people with minimum hassle.

I only have local admin rights to my own PC. This means that I would
need to persuade the sys admin to set up a SVN server on the intranet.
As I mentioned before, the company uses CVS, and so organising a SVN
server is not so straightforward (politically). I could (and I have done
it in the past) set up a server on my own PC and let people access the
server. I might go with that option.

But this doesn't really answer my original question: how do you cope
with the absolute path of 'svn:externals' if you want to mirror the SVN


Ryan Schmidt wrote:
> On Apr 12, 2007, at 03:58, TM wrote:
>> I am now going to have other people working with me in this one
>> project and I would like to use the opportunity to introduce SVN to
>> them. So I am planning to go for the easiest of approaches, which is
>> to put the vault on a shared drive on the intranet, give it lax
>> permissions and have everyone access it locally (file:). If I succeed
>> in persuading other people to see the light, then I would setup a
>> server (access the vault through svn:)
> file-protocol access is not really suited to that task. Putting a
> repository on a network drive can be problematic. For example, it is
> trivially easy for anyone with access to mount the network drive and
> delete the entire repository -- even accidentally -- with your only
> recourse being to restore it from backups, assuming you have backups
> that are current enough. Also, there is no way to lock any user out of
> any part of the repository, since any user could just copy the entire
> repository to their local drive and remove the access restrictions and
> access all of it. Please set up an svnserve (or, if you like, apache2)
> server instead. You will save yourself some headaches.
> --
> To reply to the mailing list, please use your mailer's Reply To All
> function

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Apr 13 11:06:24 2007

This is an archived mail posted to the Subversion Users mailing list.