[prev in list] [next in list] [prev in thread] [next in thread] 

List:       tortoisesvn-users
Subject:    Re: accessing an external-HD repo via windows
From:       "Simon Large" <simon.tortoisesvn () googlemail ! com>
Date:       2008-01-29 23:23:33
Message-ID: 5fad61590801291523l43c26e97h178afa214744667a () mail ! gmail ! com
[Download RAW message or body]

On 29/01/2008, Dave Lawrence <dlawrence@ad-holdings.co.uk> wrote:
>
> > You may ask why I am not using the file:// protocol since it is a local
> > repo.
> >
> > I read that one should never use Berkeley DB repositories with windows
> > network shares.
>
> I read that Berkeley DB repos should never be used with *any* sort of
> network shares not just windows.  Even the other format (FSFS) is best
> hidden away behind a server and not just shared on the network - it
> protects against viruses and accidental user damage, aswell as the
> obvious security implications.
>
>    Long term, I plan to commit to this repository from
> > various windows computers via windows-shares, so I want to be sure that
> > I always go through svnserve using the native filesystem.  From what
> > I've read the file:// protocol implies using Berkeley DB.  Though this
> > is all a little unclear.
>
> No, using file:// implies the client directly talks to the repos - and
> that *would* require file sharing for network use, but file protocol is
> not recommended for network access although this has nothing to do with
> whether or not you're using Berkeley DB - I think you've made a false
> association due to separate warnings about file sharing.
>
> > Could someone please send an example of how to refer by URL to a local
> > repository via the svn:// protocol?  I would also appreciate an example
> > of how to structure the URL when I later want to checkout
> > <vistacomputer>/testproj from <xpcomputer> when they are on the same
> > local network.
>
> svn://server/repos/project/trunk
>
> (substitute server and repos with the real names - you can also use an
> ip address if that's easier)
>
> You could test svnserve on your local PC without using the network:
> svn://localhost/repos/project/trunk
>
> You don't need to do anything to the repos to tell it how you're going
> to access it (file vs svn vs http) or what its URL is - that's all down
> to your server and network configuration.
>
> If you have existing working copies you can "relocate" them to the new
> URL from the TSVN context menu.

Please read the "Setting up a server" section in our manual.

When you start svnserve it is best to tell it where you are keeping
your repositories. Specify a parent directory which holds as many
repositories as you need and svnserve will access any repo in that
folder. The URL would be

svn://computername_or_ip/reposname/folder_inside_repository

Simon

-- 
       ___
  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.net

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org

[prev in list] [next in list] [prev in thread] [next in thread]