SCM

Creating the repository

Create the repository:

#sudo svnadmin create /usr/local/svn/newrepos

Don't forget to set the appropriate permissions for your organisation. For example, read, write and execute access for the development group, no accesses for "world". Alternatively, you can create an subversion user and set the umask

#sudo svn import mytree file:///usr/local/svn/newrepos/some/project \
    -m "Initial import"

http://svnbook.red-bean.com/nightly/en/svn-book.html#svn.reposadmin.projects.chooselayout http://svnbook.red-bean.com/nightly/en/svn-book.html#svn.tour.other.import http://svnbook.red-bean.com/nightly/en/svn-book.html#svn.serverconfig.svnserve.sshauth

This document is an overview to remind me of the steps involved, not a detailed set of instructions.

Setting up subversion

1. Setup subversion. (Use pkg_add.)
2. Create a group for people who need to use subversion. E.g. "dev" or "svn" Add users to the group.
3. Create a directory for the repository. Allow read and write permissions to the dev group; the world should have no access. Example: /home/svn/
4. Create the repository and import the files.

Connecting remotely to the repository

The svn+ssh:// URL schema is a convenient way of accessing the repository remotely, provided that active shell accounts are set up on the remote server. It uses ssh to create a temporary svnserve process. You don't need to open any ports for subversion as communications are sent over the ssh port. The svnserve process ends after closing the network connection.