At the company I work for at the moment, we have decided to use Trac as our development project management tool and ticket tracking system. This is the good news. I have worked with Trac a lot in several Open Source projects and use it for my own small developments project as well, because I like it’s simplicity and extensibility with plug-ins.
The bad news is that the company is one of those still very Microsoft-infected and when they set up the subversion repository, they used VisualSVN Server and put it on a virtual Windows 2008 Server.
So we had to install Trac on the same Windows server (side note: you can run Trac on a different host than you main Subversion repository by mirroring your repository e.g. via svnsync). This in itself wasn’t a big problem. Contrary to some information you’ll find on the net, I had no trouble getting Trac 0.11 to run under Python 2.6 and interface with Subversion 1.6.x. The current Visual SVN Server 2.0.8 comes with Subversion 1.6.6 so we need to get the Python Subversion SWIG-bindings which match this version (or at least matching 1.6.x) and our Python version. VisualSVN also has Apache 2.2.13 integrated, so we could intergrate Trac with it via mod_python or mod-wsgi, but unfortunately VisualSVN does not come with those modules and so I decided to spare me the hassle of finding a compatible mod_python binary (let alone compiling it!) and opt for running Trac standalone via the included tracd server.
This poses the question how to start and stop tracd. Being on Windows the natural choice is to run tracd as a Windows service. The steps to do so are described in the Trac documentation, but
docutils-0.6.tar.gz (optional) Install via
Pygments-1.1.1-py2.6.egg (optional) Install via
easy_install -f . Pygments-1.1.1-py26.egg
pytz-2009p-py2.6.egg (optional) Install via
easy_install -f . pytz-2009p-py26.egg
- rktools.exe (Windows Resource Kit 2003)