() With your firewall issues you will probably be better served with the
() distributed VCS tools, like Mercurial, Git, etc... They give each
() developer a full copy of the repository, so they won't need to be
() accessing over the network all the time. However, they are more
() complex.
Both Tortoise and command line svn work nicely over SSH so
you only need to poke a single hole through the firewall. In
the authorized_keys file on the server you can restrict every
user's key to only run svnserve in case general ssh access is
considered harmful.
Not sure how you mean "accessing over the network all the
time". Developers check out the source tree over the net, work
(edit/compile/run/debug) on that locally, and only need network
access again for operations like checkin, merge, or the like.
Ciao, Lobo
_______________________________________________
Discuss mailing list
Discuss@lopsa.org
http://lopsa.org/cgi-bin/mailman/listinfo/discuss
This list provided by the League of Professional System Administrators
http://lopsa.org/
