Hi > AFAICT, mod_python 3.x is required to work w/ Trac (I think this is > documented on Trac web site), and mod_python 3.x requires Apache 2.x
Ok. Thanks for this. I give this a try. I can do this on my testsystem, but unfortunately my colleague (who hosts the root server for me) is still running apache 1.3. I have seen the info on the trac website and it basically says: "For those stuck with Apache 1.3, it is also possible to get Trac 0.8.4 working with mod_python 2.7 (see TracModPython2.7). This hasn't been tested with Trac 0.9, so it may or may not work." So it should work, but I might get errors as it has not been tested. This brings me back to my original question: >> Problem now: >> When I access http://myserver/projects/whatever it just lists me the >> contents of the /var/www/projects/whatever directory. Shouldn't it pass >> processing of this folder to mod_python? The <Location> directive works, I >> just added a few dummy lines like "Require valid-user" and when I reloaded, >> it asked me for a username. So it seems to process the <Location >> /projects/whatever> directive correctly. >> >> I think I should not put the trac project environment in this >> /var/www/projects/whatever folder. But what else to put there? Just the >> htdocs folder? Is it correct to store the trac project in a patch underneath the docroot or does /projects/whatever have to point to a different directory - if so, which one? Regards Samuel --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users -~----------~----~----~----~------~----~------~--~---
