How to Set up a Linux Server with Subversion and Trac

I love Subversion and Trac too! I'm no Linux Whiz, so I chose to go with http://www.cvsdude.org/. They offer a free account for testing and it's not too pricey for the options either. Saves me a lot of headaches and time.

I also use the TortoiseSVN Client. It integrates really nicely into the Explorer interface, so you just right-click to Commit a file :)

J

I saw that SourceSecure was merged with CVSDude... I'm more comfortable running my own server locally, to be honest. To each his own. :-)

I use a combination of TortoiseSVN, Subclipse, and AnkhSVN for my development. Works great!

Nice tutorial. I just setup a subversion+trac server for a client. I was a Centos distro so most of the work was done via yum :p

I preffered using an apache server instead of the built-in trac webserver. BTW, this reminds me i need to try lighttpd. I've heard great things about it.

Thanks for the tuto! :)

Ah yes. Hey did you post this to Trac's site. They always need this type of stuff. Could do Apache? Why didn't you ask could have given you the config files and you would be all done. Also on Windows version I believe Clearsilver does not need to be installed.

Boy, couldn't setup Apache, lol.

Ah Kev, give me a break - when we worked at NC together you were the one that handled setting up Apache. It's not in my domain of expertise, so even simple tasks like setting up users and granting access to only certain projects and such is slightly beyond me. Like I said, in the past I've always dealt with IIS, and I don't have much experience in configuring Linux servers. :-)

Hi Darron,

I was thinking in change CVS system at work to SVN, but as we are using mainly Eclipse to interface CVS I'd like to know if the SVN Eclipse plugin is mature enough to work with. please could you post a comment about it? is Subeclipse stable?

Many thanks for the post :)

Hi Carlos,

I've been using Subclipse for a long time without issue. I would say it's very stable. As a backup, just in case, I also have TortoiseSVN installed. Between the two of them you won't have any problems.

Thanks for the tutorial. before I found this I had an old P3 running gentoo linux and subversion but was having trouble configuring a few things. Again thanks for the help

Crystal clear!
Well done, Darron, it saved me a lot of time. Thanks.

to make this apache2 ready, here are the working steps, basically this is exact the same as /usr/share/doc/packages/subversion/README.SuSE

this is done on suse 10.0 (eval DVD)

1. download needed
download subversion-server from ftp://chuck.ucs.indiana.edu/pub/array2/linux/opensuse/distribution/SL-10.0-OSS/inst-source/suse/x86_64/subversion-server-1.2.3-2.x86_64.rpm

2. install subversion_server
rpm -Uvh subversion-server

3. config
vi /etc/sysconfig/apache2
then add 'dav dav_svn' to setting $APACHE_MODULES

To load the configuration for a certain
virtual host, add
Include /etc/apache2/conf.d/subversion.conf
or
Include /path/to/your_subversion_configuration
in the respective virtual host configuration. This *may* be done in the default
virtual host (/etc/apache2/default-server.conf).

Add the http repository data to /etc/apache2/conf.d/subversion.conf:
#------------------------------------------------------------------------
#
# project related HTML files
#

Alias /repos "/home/svn/html"

Options +Indexes +Multiviews -FollowSymLinks
IndexOptions FancyIndexing \
ScanHTMLTitles \
NameWidth=* \
DescriptionWidth=* \
SuppressLastModified \
SuppressSize

order allow,deny
allow from all

# project repository files for project1

DAV svn
SVNPath /home/svn/repos/project1

# Limit write access to certain people
AuthType Basic
AuthName "Authorization for project1 required"
AuthUserFile /home/svn/user_access/project1_passwdfile
AuthGroupFile /home/svn/user_access/project1_groupfile

Require group project1_committers

# Limit read access to certain people

Require group project1_committers
Require group project1_readers

# project repository files for project2

DAV svn
SVNPath /home/svn/repos/project2

# Limit write permission to list of valid users.

# Require SSL connection for password protection.
# SSLRequireSSL

AuthType Basic
AuthName "Authorization for project2 required"
AuthUserFile /home/svn/user_access/project2_passwdfile
Require valid-user

#------------------------------------------------------------------------

rcapache2 restart
or
/etc/init.d/apache2 restart

4. user and filesystem
groupadd svn
useradd svn -G svn

create a few directories:
mkdir -p /home/svn/repos
mkdir -p /home/svn/user_access
mkdir -p /home/svn/html

# to create the repositories itself:
cd /home/svn/repos
svnadmin create project1
chown -R wwwrun:www project1/{dav,db,locks}
svnadmin create project2
chown -R wwwrun:www project2/{dav,db,locks}

# Now create the user access files:
# project1 is a restricted project. read access requires a password. write access is limited to a few users
touch /home/svn/user_access/project1_passwdfile
chown root:www /home/svn/user_access/project1_passwdfile
chmod 640 /home/svn/user_access/project1_passwdfile

htpasswd2 /home/svn/user_access/project1_passwdfile olaf
htpasswd2 /home/svn/user_access/project1_passwdfile olh

# this is the group file for project1:
/home/svn/user_access/project1_groupfile
# content:
project1_committers: olh
project1_readers: olaf olh

# project2 is world readable, but only a few can commit to the sources.
touch /home/svn/user_access/project2_passwdfile
chown root:www /home/svn/user_access/project2_passwdfile
chmod 640 /home/svn/user_access/project2_passwdfile
htpasswd2 /home/svn/user_access/project2_passwdfile olaf

# Now import the data, e.g.
svn import /path/to/project1-tree http://host/repos/project1
svn import /path/to/project2-tree http://host/repos/project2

5 test and done
# You should be able to connect to the server:
http://host/repos/project2
http://host/repos/project1

Great.

htpasswd2: command not found

This is frustrating.