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

allowing outside access to subversion repositories - best practices

From: Hanback, Phillip <Phillip.Hanback_at_avocent.com>
Date: Mon, 7 Dec 2009 14:18:07 -0600

Good afternoon. I am an administrator in charge of a fairly large
subversion environment. We normally access the repositories using Apache
to serve on port 443. At this point in time, all of our servers are
internal access only. Recently we've had a request to open up one of the
repositories to a few developers outside of the company. There have been
several strategies for accomplishing this goal. Security is of paramount
importance. Some of the suggestions that have been tossed about are VPN
access using firewall ACLs to limit access to only the required
subversion server, setup of a new server supporting only the one repo
and put it in the DMZ, one of the developers had suggested that the "old
way" was to send tarballs of their code to be manually loaded into our
internal subversion repo. To me this last option brings up questions of
how to resolve conflicts in files normally decided by the developers.
I'm just looking for some feedback from people with more subversion
experience than me. Maybe one of you have had similar requests in the
past and you could share your experience and wisdom on the subject. All
responses appreciated. Thanks.

 

 

Phill

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2427932

Please start new threads on the <users_at_subversion.apache.org> mailing list.
To subscribe to the new list, send an empty e-mail to <users-subscribe_at_subversion.apache.org>.
Received on 2009-12-07 21:19:18 CET

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.