Calendar

Sponsors

RSS

About

This is a collection of video tutorials on anything to help developers of all standards. Ranging from ColdFusion to Source Control and Automated Builds.

So what are these files in the Configuration Folder Kev?

Posted At : January 21, 2008 8:55 PM | Posted By : Inner Rhythm TV
Related Categories: Windows , Apache , Python , Subversion , TortoiseSVN , Trac

So to speed up the quick deployment of SAT (Subversion, Apache & Trac) I had some files pre-configured which you may need to edit yourself to change the locations if you don't follow my tutorials to the letter.

I do suggest you at least try to at first maybe on the Virtual Machine just so you know you have it right before doing it on a live server. (There is an issue with IP Addresses and IIS binding to all of them on Port 80, but I hope to cover that soon)

Ok So what are these files well these are:

  1. Subversion.conf
  2. svn-acl
  3. Trac.conf

Subversion.conf

This file contains the configuration for Subversion with in Apache.

<Location /SVN/Project1>
DAV svn
SVNPath C:/Data/SVNRepos/Project1

AuthType Basic
AuthName "Subversion Project1 repository"
AuthUserFile C:/Data/Configuration/svn-auth-file

Require valid-user

AuthzSVNAccessFile C:/Data/Configuration/svn-acl
</Location>

SVNPath: This is the path to the SVN Repository

AuthName: Is the ream to use (Not really sure myself but I tend to change this for each)

AuthUserFile: This is the user file to use, this is created in the tutorial.

AuthzSVNAccessFile: This is the access control list.

svn-acl

This is the Access Control List and allows you to specigy which users / groups of users have access to which parts of the repository.


#
# specify groups here
#
[groups]
team1 = Admin, User

#
# team1 group has a read/write access to project1 repository
# all subdirectories
# all others have read access only
#
[Project1:/]
@team1 = rw
* = r

The Example used has created a group called team1 which has Admin and User as members. We then are able to Specify that All members of the group team1 have read / write access to the whole repository and all other users have read only. After the forward slash within [Project1:/] You can specify folders within your repository and give even more fine grade access.

Trac.comnf

This is the Apache config for the Trac install.

<LocationMatch "/Trac/[^/]+/login">
AuthType Basic
AuthName "Trac"
AuthUserFile C:/Data/Configuration/svn-auth-file
Require valid-user
</LocationMatch>

<Location /Trac>
SetHandler mod_python
PythonInterpreter main_interpreter
PythonHandler trac.web.modpython_frontend
PythonOption TracEnvParentDir C:/Data/TracRepos
PythonOption TracUriRoot /Trac
</Location>

The first section informs trac to pop up the login form for all users that try to access login, and thus allows them to login.

THe second part adds the location /Trac to the URL and will list each instance of trac installed.

CopyText.txt

I of course can't leave out copytext.txt this is just the addins required to the Apache Config file in one place and saves typing and types:


#Subversion Modules
LoadModule dav_module modules/mod_dav.so
LoadModule dav_svn_module C:\Apps\Subversion\bin\mod_dav_svn.so
LoadModule authz_svn_module C:\Apps\Subversion\bin\mod_authz_svn.so

Include C:/Data/Configuration/Subversion.conf

Include C:/Data/Configuration/Trac.conf

I hope this clears up what is going on and I of course hope that you too can install SAT in under 20 minutes :) Well with practice :)

If you have any questions please leave a comment or contact me using the link above.

All comments appreciated, and I will have to admit I haven't had time to proof read each one as I wanted to get this out as a little B-Day Present form me to you all :)

Comments