Routing Apache TracEnv

Question

i have a situation with many trac instances. They all have the same structure in the filesystem.

PATH/trac1
PATH/trac2
PATH/trac3

i have this configuration

<Location /trac/trac1>
 SetHandler mod_python
 PythonInterpreter main_interpreter
 PythonHandler trac.web.modpython_frontend 
 PythonOption TracEnv PATH/trac1
 PythonOption TracUriRoot /trac/trac1
 PythonOption PYTHON_EGG_CACHE PATH/eggs/
</Location>
<Location /trac/trac2>
 SetHandler mod_python
 PythonInterpreter main_interpreter
 PythonHandler trac.web.modpython_frontend 
 PythonOption TracEnv PATH/trac2
 PythonOption TracUriRoot /trac/trac2
 PythonOption PYTHON_EGG_CACHE PATH/eggs/
</Location>
<Location /trac/trac3>
 SetHandler mod_python
 PythonInterpreter main_interpreter
 PythonHandler trac.web.modpython_frontend 
 PythonOption TracEnv PATH/trac3
 PythonOption TracUriRoot /trac/trac3
 PythonOption PYTHON_EGG_CACHE PATH/eggs/
</Location>

i wonder if it's possible to do something like (TracEnvParentDir is not an option)

<Location /trac/{ENV}>
 SetHandler mod_python
 PythonInterpreter main_interpreter
 PythonHandler trac.web.modpython_frontend 
 PythonOption TracEnv PATH/{ENV}
 PythonOption TracUriRoot /trac/{ENV}
 PythonOption PYTHON_EGG_CACHE PATH/eggs/
</Location>

Thank you for your time.

EDIT: TracEnvParentDir is not an option because my structure is the following

+---projs
    +---trac1
    ¦   +---public [instance]
    ¦   +---t1
    ¦   ¦   +---common [instance]
    ¦   ¦   +---g1 [instance]
    ¦   ¦   +---g2 [instance]
    ¦   ¦   +---g3 [instance]
    ¦   ¦   +---g4 [instance]
    ¦   ¦   +---g5 [instance]
    ¦   +---t2
    ¦   ¦   +---common [instance]
    ¦   ¦   +---g1 [instance]
    ¦   ¦   +---g2 [instance]
    ¦   ¦   +---g3 [instance]
    ¦   ¦   +---g4 [instance]
    ¦   ¦   +---g5 [instance]
    ¦   +---t3
    ¦       +---common [instance]
    ¦       +---g1 [instance]
    ¦       +---g2 [instance]
    ¦       +---g3 [instance]
    ¦       +---g4 [instance]
    ¦       +---g5 [instance]
    ¦  
    +---trac2
        +---public [instance]
        +---t1
        ¦   +---common [instance]
        ¦   +---g1 [instance]
        ¦   +---g2 [instance]
        ¦   +---g3 [instance]
        ¦   +---g4 [instance]
        ¦   +---g5 [instance]
        +---t2
        ¦   +---common [instance]
        ¦   +---g1 [instance]
        ¦   +---g2 [instance]
        ¦   +---g3 [instance]
        ¦   +---g4 [instance]
        ¦   +---g5 [instance]
        +---t3
            +---common [instance]
            +---g1 [instance]
            +---g2 [instance]
            +---g3 [instance]
            +---g4 [instance]
            +---g5 [instance]

I use the TracEnvParentDir on t1, t2 and t3 and TracEnv on trac1/public and trac2/public

I wonder if it's possible to define a part of the url variable.

Can you explain why `TracEnvParentDir` is not an option? – retracile Jun 04 '10 at 13:47 — retracile, Jun 04 '10 at 13:47

score 0 · Accepted Answer · edited Apr 13 '17 at 12:14

0

You may want to switch to mod_wsgi instead of modpython, and see my answer here how to do what you want: Dynamic subdomains, mod_python and trac

edited Apr 13 '17 at 12:14

Community

1

answered Jun 04 '10 at 22:32

silk

918
5
13

score 0 · Answer 2 · answered Jun 06 '10 at 12:53

0

The official mod_wsgi documentation on integrating Trac with mod_wsgi tells you about how to do this. See:

http://code.google.com/p/modwsgi/wiki/IntegrationWithTrac

answered Jun 06 '10 at 12:53

Graham Dumpleton

5,990
2
20
19

Routing Apache TracEnv

2 Answers2