Hello,
Thanks, and apologies if this is a repeat message.
I'm not really wanting to do an apache setup for this project. What my structure will be like I think will be /var/svn and under that parent directory repos# where that equals a separate project.
I've read that svnserve can hook in to sasl for encryption and authentication, but not a lot of details on it. I'm starting to think my best method would be svn+ssh, any experiences with this method?
Thanks. Dave.
On 7/15/11, Les Mikesell lesmikesell@gmail.com wrote:
On 7/15/2011 9:41 AM, David Mehler wrote:
Hello, I've got a CentOS box that i'm wanting to set up svnserve on. I've read much, and am confused. Does svnserve support data encryption and also restricting users from specific repositories?
I'm thinking of a single repo structure under /var/svn-repos and I've got two users user1 and user2, each should have access to their own projects in this case user1 can access project1 and user2 can access project2, but neither should be allowed to access the others.
My second issue is I don't want to have a access path like /var/svn-repos/project1
for instance. I've read the -r root option which I would set to:
-r /var/svn-repos
would settle this, but am not sure where to set that option so it's picked up.
I don't believe svnserve provides encryption, but it is not the only way to remotely access subversion repositories. You can also use http(s) with mod_dav_svn or svn+ssh which the clients understand natively. You can set up path-based authorization but that and authentication will depend on which access method(s) you use.
Details here: http://svnbook.red-bean.com/nightly/en/svn-book.html
It is somewhat painful to re-arrange repositories/contents after they grow large, so unless your projects share components it might be better to have separate repositories under the same root directory.
-- Les Mikesell lesmikesell@gmail.com
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos