RAD Lab uses SVN along with SSH public keys to manage source code development and other documents that undergo revision.
Access to existing repositories are authenticated via SSH keys.
Currently, access to existing SVN repositories is provided by scm.millennium.berkeley.edu. To access an existing repository:
$ svn command [options] svn+ssh://email@example.com/repo/<repo path>
We currently only support access via svn+ssh.
Access to the repositories is controlled via SSH keys installed in the <radsvn> account.
If you have access to scm.millennium.berkeley.edu, you can give yourself or someone else access to the SVN repository by following these steps:
~radsvn/.ssh/authorized_keysand add your or someone else's SSH public key to grant yourself or someone else access.
sudo -u radsvn vi ~radsvn/.ssh/authorized_keys
$ svn list [options] svn+ssh://firstname.lastname@example.org/repo/<repo path>
If you do not have access to scm.millennium.berkeley.edu, ask someone in your research group who does to do this for you. You can also mail your SSH public key to email@example.com asking for SVN access.
Note: By default, svn will look in ~/.ssh/id_rsa or ~/.ssh/id_dsa for your private ssh key. If you want to use a different key, you can use ssh-agent, but that is beyond the scope of this note.
If you run
svn list svn+ssh://firstname.lastname@example.org/repo
you will see the following:
$ svn list svn+ssh://email@example.com/repo courses/ docs/ papers/ projects/ users/ vendor/
This is a proposed hierarchy,
stolen borrowed from ICSI ParLab, to help keep things organized. Feel free to add to or modify it.