Has anyone used Subversion on a network share?
-
Here's what I'd like to do: (1) Put the repository on a network drive using FSFS. (2) Run the svnserve program from my local PC. (3) The repository should ONLY be writable by svnserve and the other subversion components. Well, (1) and (2) are fine, but I'm having terrible problems with (3). According to the Subversion docs, the recent versions should be happy running FSFS on a network drive. It's easy to set up svnserve to access the drive. BUT... there seems to be no way of specifying a user name and password to be used! Everything I've seen on the web that tells you how to set it up seems to assume that EVERYONE will have write access to the repository directory. I find this extremely bizarre, as it is so dangerous. I can't believe this would be normal practice. Or am I doing this in the wrong way? Should I just have the repository on my local disk and do a periodic xcopy of the entire repository to the network drive? (The problem is that only the network drive gets backed up).
-
Here's what I'd like to do: (1) Put the repository on a network drive using FSFS. (2) Run the svnserve program from my local PC. (3) The repository should ONLY be writable by svnserve and the other subversion components. Well, (1) and (2) are fine, but I'm having terrible problems with (3). According to the Subversion docs, the recent versions should be happy running FSFS on a network drive. It's easy to set up svnserve to access the drive. BUT... there seems to be no way of specifying a user name and password to be used! Everything I've seen on the web that tells you how to set it up seems to assume that EVERYONE will have write access to the repository directory. I find this extremely bizarre, as it is so dangerous. I can't believe this would be normal practice. Or am I doing this in the wrong way? Should I just have the repository on my local disk and do a periodic xcopy of the entire repository to the network drive? (The problem is that only the network drive gets backed up).
from what I understand, if you are using svnserve as the server, your users should not need to have access to the filesystem; and will access the repository with the
svn://protocol. for example (taken from the subversion book) :svn checkout svn://host.example.com/project1in that case, the repository does not have to be on a shared/network drive. ( check the book : http://svnbook.red-bean.com/en/1.1/svn-book.html#svn-ch-6-sect-3[^] ) if you don't want to use svnserver, then all users will have to have access to the drive, and use direct commands ( svn co .. ) without a protocol.
Maximilien Lincourt Your Head A Splode - Strong Bad
-
from what I understand, if you are using svnserve as the server, your users should not need to have access to the filesystem; and will access the repository with the
svn://protocol. for example (taken from the subversion book) :svn checkout svn://host.example.com/project1in that case, the repository does not have to be on a shared/network drive. ( check the book : http://svnbook.red-bean.com/en/1.1/svn-book.html#svn-ch-6-sect-3[^] ) if you don't want to use svnserver, then all users will have to have access to the drive, and use direct commands ( svn co .. ) without a protocol.
Maximilien Lincourt Your Head A Splode - Strong Bad
> if you don't want to use svnserver, then all users will have to have access to the drive, and use direct commands ( svn co .. ) without a protocol. Thanks, I didn't realize that you could do this. I'm actually the only developer at my company, so it's OK for all users of SVN (ie, me!) to have write access. It would still be better for me to ordinarily not have write access, but I can live with it for now. The network drives are the only ones that are backed up regularly, so the repository cannot be stored on a local drive. What I've been most concerned about is non-developers wrecking the repository by mistake. (Recently, a business manager accidentally did a drag-and-drop of dozens of crucial widely-accessable company files into his own private directory where noone else could find them :-)). Anyway, it seems as though the ability to have a repository on a network drive is practically useless for svnserve, but is very useful for a server-less configuration. Thanks again -Don