= BRICCS Trac system =

This is a page for discussing the Trac issue tracking system.

== Deployment ==
The current system is hosted on a SliceHost machine, primarily because it was quicker and easier to get it up and running on SliceHost than on one of the RCS hosted VMs.

We need to integrate the Trac system with our Subversion repository, enabling us to use links in wiki pages and bug reports to refer to sections code in svn.
In order to do this, the two systems need to be co-located on the same machine.

We have a set of bash shell scripts in svn for installing Trac and Subversion which will transfer the data from the existing systems.
The migration scripts have been tested on CentOS 5.5.

If/when RCS provides us with a RedHat based VM (Fedora, CentOS or RHEL), we are ready to migrate our Trac and Subversion services to the new machine.

== Access controls ==

The current system is configured to require password for all write access preventing external users from editing our wiki pages. However, public viewing of the trac wiki is possible, which means we are able to share things on the wiki with people outside the core BRICCS development team.

Based on experience with AstroGrid, the ability to point from people outside the project at pages on our wiki was extremely useful for facilitating discussion and getting advice and ideas from people outside the project.

== Password database ==

The current system uses a simple htacces password file to handle user authentication.

Add passwords to the password file (crypt encrypted by default) by:
[root@briccs-7 trac]# htpasswd /var/local/briccs/trac/conf/briccs.htpasswd firstname.surname

There is a Trac module for storing passwords in a database, which should makes managing user accounts and passwords a lot easier. We should consider whether we need to install this before we issue passwords to the hospital staff. Depends how many people need write access.