This is not a tutorial. There is a good one on the TracWiki. I just want to tell everyone, that if you ever consider installing Trac on Windows, then just don’t do it and install it on a *nix machine. This will save you a lot of time and nerves. There are even pre-build environments available with SVN, Trac and Cruisecontrol.
I spent almost an entire day to configure Trac on Windows. It’s not funny. If you have to do it, be sure to use the mod_python setup. It’s far easier to install than trying to set up CGI on a Windows box (which I think would be the first and easiest setup on *nix machines). I may not be the smartest person on earth but the Apache error messages on Windows are just plain useless. I don’t care if it’s Apache’s fault, Windows’ fault or my own. It’s just broken.
So if you have no other choice than using Windows, make sure that you use a plain Apache from apache.org – No xampp, Typo 3 package or anything like that. Some of these packages come with their own version of Python which really fucks things up, if it’s not the version you need). This will save you a lot of trouble.
The main problem we had here was the “We already have an Apache on this server, so why not install on this one?”-thing. The Apache installation turned out to be one of the packages mentioned above which made things not really easier.
Related Posts
- Small differences that matter - Small things I like about Mac OS X that Windows doesn't have
- Windows Task manger fun - I had a lot of fun with windows task manager... again
- Remote system management using MS Windows - Remote management with Windows is really painful sometimes.
- Blog-what? - Funny dictionary thin with blogdesk