-

Difference between revisions of "SVN-Developers"

From Open Bioinformatics Foundation
Jump to: navigation, search
 
Line 1: Line 1:
 +
= SVN repository access for developers =
 +
 
This page is for open-bio affiliated developers who are making use of SVN based version control systems rather than the traditional CVS based systems.  
 
This page is for open-bio affiliated developers who are making use of SVN based version control systems rather than the traditional CVS based systems.  
  
 +
== Access methods ==
 +
=== svnserve operates in tunnel mode only ===
 +
For security and access control reasons we are not running a daemonized svnserver process or allowing access via HTTP through the Apache mod_DAV/svn module methods. The SVN access method that fits best with our current developer and security model is to run svnserver in "tunnel" mode on a per-user basis. This means developers will connect and authenticate via encrypted SSH sessions before svnserver is invoked. In this scenario svnserver is launched in tunnel mode and runs <em>as the user who invoked it</em>.
  
For security and access control reasons we are not running a daemonized svnserver process or allowing access via HTTP through the Apache mod_DAV/svn module methods. The SVN access method that fits best with our current developer and security model is to run svnserver in "tunnel" mode on a per-user basis. This means developers will connect and authenticate via encrypted SSH sessions before svnserver is invoked. In this scenario svnserver is launched in tunnel mode and runs <em>as the user who invoked it</em>.
+
== Hosted repositories ==
 +
===blipkit==
 +
Blipkit access is achieved via methods such as this:
 +
<code>
 +
svn checkout svn+ssh://dev.open-bio.org/home/svn-repositories/blipkit
 +
</code>

Revision as of 13:07, 28 March 2006

SVN repository access for developers

This page is for open-bio affiliated developers who are making use of SVN based version control systems rather than the traditional CVS based systems.

Access methods

svnserve operates in tunnel mode only

For security and access control reasons we are not running a daemonized svnserver process or allowing access via HTTP through the Apache mod_DAV/svn module methods. The SVN access method that fits best with our current developer and security model is to run svnserver in "tunnel" mode on a per-user basis. This means developers will connect and authenticate via encrypted SSH sessions before svnserver is invoked. In this scenario svnserver is launched in tunnel mode and runs as the user who invoked it.

Hosted repositories

=blipkit

Blipkit access is achieved via methods such as this: svn checkout svn+ssh://dev.open-bio.org/home/svn-repositories/blipkit