Network shares will slow down Subversion, but I've used FSFS over NFS
before. However, this was done because the actual drive is on a disk
server, but we still used svn:// or http:// to access the repository.
Is this on a network share, so you can simply use file://? That's not
a good idea. I never use file:// even when the repository sits in my
HOME directory and I am the only one using the repository. It's simple
enough to start up svnserver and avoid file:// entirely. Then, you
really don't need a network share. Plus, the permission setting of
svnserver is pretty straight forward. It's perfect for small
repositories -- even one used by only a single user.
On Mon, Feb 23, 2009 at 12:29 PM, James An <james_at_jamesan.ca> wrote:
> I've created an FSFS repository and would like to put it in a remote network
> location that is regularly backed-up.
> I've read that it's poor practice to directly access repos over a network
> and that I should set up svnserve or Apache. The SVN book mentions that
> network shares are bad for BDB repos, but doesn't really comment on its use
> for FSFS ones. Some people say there are potential problems for network
> repos that are accessible by multiple users.
> If the FSFS repo (on a network share) is restricted so only a single user
> can access it, are there any risks to directly accessing the repo with an
> SVN client? If I extend the permissions so that multiple users can read-only
> access the repo, but only one user can write to it, are there any additional
> risks? If so, is there any way to mitigate those risks without a local SVN
> server at that location?
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-02-24 20:15:44 CET