> but what is /projects set to? Not sure to understand the question:
When you use TracParentEnv, it means that the directory you specify with this directive harbors several Trac projects Using the previous example, let's define three projects: trac-admin /v01/trac/trac1 initenv trac-admin /v01/trac/trac2 initenv trac-admin /v01/trac/tracx initenv To access these projects you either need to define on Location directive per project: <Location /projects/trac1> ... PythonOption TracEnv /v01/trac1 </Location> <Location /projects/trac2> ... PythonOption TracEnv /v01/trac2 </Location> <Location /projects/tracx> ... PythonOption TracEnv /v01/tracx </Location> or to save some typing and config duplication, you can use <LocationMatch /projects/[[:alnum:]]+> PythonOption TracParentEnv /v01 </LocationMatch> with the latter config, it means that any child directory within the /v01 directory will be considered as a potential Trac project, and this project will be accessed through the web with its directory name appended to the parent directory: http://server/projects/ + directory name, for example http://server/projects/trac1, exactly as if you define one <Location> block per project. Nevertheless, I *highly* recommend that you first install a single Trac project with a TracEnv directive, validate that it works as expected, before attempting to move forward and install several other projects. One step after another ;-) Cheers, Manu --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
