Changes between Version 1 and Version 2 of TracModPython


Ignore:
Timestamp:
2023-04-20T18:30:58Z (19 months ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • TracModPython

    v1 v2  
    1 = Trac and mod_python =
    21[[TracGuideToc]]
    32
     3= Trac and mod_python
     4
     5Mod_python is an [https://httpd.apache.org/ Apache] module that embeds the Python interpreter within the server, so that web-based applications in Python will run many times faster than traditional CGI and will have the ability to retain database connections.
    46Trac supports [http://www.modpython.org/ mod_python], which speeds up Trac's response times considerably, especially compared to [TracCgi CGI], and permits use of many Apache features not possible with [wiki:TracStandalone tracd]/mod_proxy.
    57
    6 These instructions are for Apache 2; if you are still using Apache 1.3, you may have some luck with [trac:wiki:TracModPython2.7 TracModPython2.7].
    7 
    8 == Simple configuration ==
     8[[PageOutline(2-3,Overview,inline)]]
     9
     10== Simple configuration: single project #Simpleconfiguration
    911
    1012If you just installed mod_python, you may have to add a line to load the module in the Apache configuration:
    11 {{{
     13{{{#!apache
    1214LoadModule python_module modules/mod_python.so
    1315}}}
    1416
    15 ''Note: The exact path to the module depends on how the HTTPD installation is laid out.''
    16 
    17 On Debian using apt-get
    18 {{{
     17'''Note''': The exact path to the module depends on how the HTTPD installation is laid out.
     18
     19On Debian using apt-get:
     20{{{#!sh
    1921apt-get install libapache2-mod-python libapache2-mod-python-doc
    2022}}}
    21 (Still on Debian) after you have installed mod_python, you must enable the modules in apache2 (equivalent of the above Load Module directive):
    22 {{{
    23 a2enmod mod_python
    24 }}}
     23
     24Still on Debian, after you have installed mod_python, you must enable the modules in apache2, equivalent to the above Load Module directive:
     25{{{#!sh
     26a2enmod python
     27}}}
     28
    2529On Fedora use, using yum:
    26 {{{
     30{{{#!sh
    2731yum install mod_python
    2832}}}
    29 You can test your mod_python installation by adding the following to your httpd.conf.  You should remove this when you are done testing for security reasons. Note: mod_python.testhandler is only available in mod_python 3.2+.
    30 {{{
    31 #!xml
     33
     34You can test your mod_python installation by adding the following to your httpd.conf. You should remove this when you are done testing for security reasons. Note: mod_python.testhandler is only available in mod_python 3.2+.
     35{{{#!apache
    3236<Location /mpinfo>
    33    SetHandler mod_python
    34    PythonInterpreter main_interpreter
    35    PythonHandler mod_python.testhandler
     37  SetHandler mod_python
     38  PythonInterpreter main_interpreter
     39  PythonHandler mod_python.testhandler
     40  # For Apache 2.2
     41  <IfModule !mod_authz_core.c>
     42    Order allow,deny
     43    Allow from all
     44  </IfModule>
     45  # For Apache 2.4
     46  <IfModule mod_authz_core.c>
     47    Require all granted
     48  </IfModule>
    3649</Location>
    3750}}}
    3851
    3952A simple setup of Trac on mod_python looks like this:
    40 {{{
    41 #!xml
     53{{{#!apache
    4254<Location /projects/myproject>
    43    SetHandler mod_python
    44    PythonInterpreter main_interpreter
    45    PythonHandler trac.web.modpython_frontend
    46    PythonOption TracEnv /var/trac/myproject
    47    PythonOption TracUriRoot /projects/myproject
    48 </Location>
    49 }}}
    50 
    51 The option '''`TracUriRoot`''' may or may not be necessary in your setup. Try your configuration without it; if the URLs produced by Trac look wrong, if Trac does not seem to recognize URLs correctly, or you get an odd "No handler matched request to..." error, add the '''`TracUriRoot`''' option.  You will notice that the `Location` and '''`TracUriRoot`''' have the same path.
    52 
    53 The options available are
    54 {{{
    55     # For a single project
    56     PythonOption TracEnv /var/trac/myproject
    57     # For multiple projects
    58     PythonOption TracEnvParentDir /var/trac/myprojects
    59     # For the index of multiple projects
    60     PythonOption TracEnvIndexTemplate /srv/www/htdocs/trac/project_list_template.html
    61     # A space delimitted list, with a "," between key and value pairs.
    62     PythonOption TracTemplateVars key1,val1 key2,val2
    63     # Useful to get the date in the wanted order
    64     PythonOption TracLocale en_GB.UTF8
    65     # See description above       
    66     PythonOption TracUriRoot /projects/myproject
    67 }}}
    68 
    69 === Python Egg Cache ===
    70 
    71 Compressed python eggs like Genshi are normally extracted into a directory named `.python-eggs` in the users home directory. Since apache's home usually is not writable an alternate egg cache directory can be specified like this:
    72 {{{
    73 PythonOption PYTHON_EGG_CACHE /var/trac/myprojects/egg-cache
    74 }}}
    75 
    76 or you can uncompress the Genshi egg to resolve problems extracting from it.
    77 === Configuring Authentication ===
    78 
    79 Creating password files and configuring authentication works similar to the process for [wiki:TracCgi#AddingAuthentication CGI]:
    80 {{{
    81 #!xml
    82 <Location /projects/myproject/login>
    83   AuthType Basic
    84   AuthName "myproject"
    85   AuthUserFile /var/trac/myproject/.htpasswd
    86   Require valid-user
    87 </Location>
    88 }}}
    89 
    90 Configuration for mod_ldap authentication in Apache is a bit tricky (httpd 2.2.x and OpenLDAP: slapd 2.3.19)
    91 
    92 1. You need to load the following modules in Apache httpd.conf
    93 {{{
    94 LoadModule ldap_module modules/mod_ldap.so
    95 LoadModule authnz_ldap_module modules/mod_authnz_ldap.so
    96 }}}
    97 
    98 2. Your httpd.conf also needs to look something like:
    99 
    100 {{{
    101 #!xml
    102 <Location /trac/>
    10355  SetHandler mod_python
    10456  PythonInterpreter main_interpreter
    10557  PythonHandler trac.web.modpython_frontend
    106   PythonOption TracEnv /home/trac/
    107   PythonOption TracUriRoot /trac/
    108   Order deny,allow
    109   Deny from all
    110   Allow from 192.168.11.0/24
    111   AuthType Basic
    112   AuthName "Trac"
    113   AuthBasicProvider "ldap"
    114   AuthLDAPURL "ldap://127.0.0.1/dc=example,dc=co,dc=ke?uid?sub?(objectClass=inetOrgPerson)"
    115   authzldapauthoritative Off
    116   require valid-user
    117 </Location>
    118 }}}
    119 
    120 Or the LDAP interface to a Microsoft Active Directory:
    121 
    122 {{{
    123 #!xml
    124 <Location /trac/>
     58  PythonOption TracEnv /var/trac/myproject
     59  PythonOption TracUriRoot /projects/myproject
     60  # For Apache 2.2
     61  <IfModule !mod_authz_core.c>
     62    Order allow,deny
     63    Allow from all
     64  </IfModule>
     65  # For Apache 2.4
     66  <IfModule mod_authz_core.c>
     67    Require all granted
     68  </IfModule>
     69</Location>
     70}}}
     71
     72The option '''`TracUriRoot`''' may or may not be necessary in your setup. Try your configuration without it; if the URLs produced by Trac look wrong, if Trac does not seem to recognize URLs correctly, or you get an odd "No handler matched request to..." error, add the '''`TracUriRoot`''' option. You will notice that the `Location` and '''`TracUriRoot`''' have the same path.
     73
     74The options available are:
     75{{{#!apache
     76# For a single project
     77PythonOption TracEnv /var/trac/myproject
     78
     79# For multiple projects
     80PythonOption TracEnvParentDir /var/trac/myprojects
     81
     82# For the index of multiple projects
     83PythonOption TracEnvIndexTemplate /srv/www/htdocs/trac/project_list_template.html
     84
     85# A space delimited list, with a "," between key and value pairs.
     86PythonOption TracTemplateVars key1,val1 key2,val2
     87
     88# Useful to get the date in the wanted order
     89PythonOption TracLocale en_GB.UTF8
     90
     91# See description above
     92PythonOption TracUriRoot /projects/myproject
     93}}}
     94
     95=== Python Egg Cache
     96
     97Compressed Python eggs like Genshi are normally extracted into a directory named `.python-eggs` in the users home directory. Since Apache's home usually is not writeable, an alternate egg cache directory can be specified like this:
     98{{{#!apache
     99PythonOption PYTHON_EGG_CACHE /var/trac/myprojects/egg-cache
     100}}}
     101
     102Or you can uncompress the Genshi egg to resolve problems extracting from it.
     103
     104=== Configuring Authentication
     105
     106See corresponding section in the [wiki:TracModWSGI#ConfiguringAuthentication] page.
     107
     108== Advanced Configuration
     109
     110=== Setting the Python Egg Cache
     111
     112If the Egg Cache isn't writeable by your Web server, you'll either have to change the permissions, or point Python to a location where Apache can write. This can manifest itself as a `500 internal server error` and/or a complaint in the syslog.
     113
     114{{{#!apache
     115<Location /projects/myproject>
     116  ...
     117  PythonOption PYTHON_EGG_CACHE /tmp
     118  ...
     119</Location>
     120}}}
     121
     122=== Setting the !PythonPath
     123
     124If the Trac installation isn't installed in your Python path, you will have to tell Apache where to find the Trac mod_python handler  using the `PythonPath` directive:
     125{{{#!apache
     126<Location /projects/myproject>
     127  ...
     128  PythonPath "sys.path + ['/path/to/trac']"
     129  ...
     130</Location>
     131}}}
     132
     133Be careful about using the !PythonPath directive, and ''not'' `SetEnv PYTHONPATH`, as the latter won't work.
     134
     135=== Setting up multiple projects
     136
     137The Trac mod_python handler supports a configuration option similar to Subversion's `SvnParentPath`, called `TracEnvParentDir`:
     138{{{#!apache
     139<Location /projects>
    125140  SetHandler mod_python
    126141  PythonInterpreter main_interpreter
    127142  PythonHandler trac.web.modpython_frontend
    128   PythonOption TracEnv /home/trac/
    129   PythonOption TracUriRoot /trac/
    130   Order deny,allow
    131   Deny from all
    132   Allow from 192.168.11.0/24
    133   AuthType Basic
    134   AuthName "Trac"
    135   AuthBasicProvider "ldap"
    136   AuthLDAPURL "ldap://adserver.company.com:3268/DC=company,DC=com?sAMAccountName?sub?(objectClass=user)"
    137   AuthLDAPBindDN       ldap-auth-user@company.com
    138   AuthLDAPBindPassword "the_password"
    139   authzldapauthoritative Off
    140   # require valid-user
    141   require ldap-group CN=Trac Users,CN=Users,DC=company,DC=com
    142 </Location>
    143 }}}
    144 
    145 Note 1: This is the case where the LDAP search will get around the multiple OUs, conecting to Global Catalog Server portion of AD (Notice the port is 3268, not the normal LDAP 389). The GCS is basically a "flattened" tree which allows searching for a user without knowing to which OU they belong.
    146 
    147 Note 2: Active Directory requires an authenticating user/password to access records (AuthLDAPBindDN and AuthLDAPBindPassword).
    148 
    149 Note 3: The directive "require ldap-group ..."  specifies an AD group whose members are allowed access.
    150 
    151 
    152 === Setting the Python Egg Cache ===
    153 
    154 If the Egg Cache isn't writeable by your Web server, you'll either have to change the permissions, or point Python to a location where Apache can write. This can manifest itself as a ''500 internal server error'' and/or a complaint in the syslog.
    155 
    156 {{{
    157 #!xml
    158 <Location /projects/myproject>
    159   ...
    160   PythonOption PYTHON_EGG_CACHE /tmp
    161   ...
    162 </Location>
    163 }}}
    164 
    165 
    166 === Setting the !PythonPath ===
    167 
    168 If the Trac installation isn't installed in your Python path, you'll have to tell Apache where to find the Trac mod_python handler  using the `PythonPath` directive:
    169 {{{
    170 #!xml
    171 <Location /projects/myproject>
    172   ...
    173   PythonPath "sys.path + ['/path/to/trac']"
    174   ...
    175 </Location>
    176 }}}
    177 
    178 Be careful about using the !PythonPath directive, and ''not'' `SetEnv PYTHONPATH`, as the latter won't work.
    179 
    180 == Setting up multiple projects ==
    181 
    182 The Trac mod_python handler supports a configuration option similar to Subversion's `SvnParentPath`, called `TracEnvParentDir`:
    183 {{{
    184 #!xml
    185 <Location /projects>
    186   SetHandler mod_python
    187   PythonInterpreter main_interpreter
    188   PythonHandler trac.web.modpython_frontend
    189143  PythonOption TracEnvParentDir /var/trac
    190144  PythonOption TracUriRoot /projects
    … …  
    194148When you request the `/projects` URL, you will get a listing of all subdirectories of the directory you set as `TracEnvParentDir` that look like Trac environment directories. Selecting any project in the list will bring you to the corresponding Trac environment.
    195149
     150Directories residing in `TracEnvParentDir` that are not environment directories will display an error message on the [TracInterfaceCustomization#ProjectList project index page]. The directories can be excluded by listing them in a `.tracignore` file residing in `TracEnvParentDir`. Unix [https://docs.python.org/2/library/fnmatch.html shell-style wildcard patterns] can be used in the newline separated list of directories.
     151
    196152If you don't want to have the subdirectory listing as your projects home page you can use a
    197 {{{
    198 #!xml
     153{{{#!apache
    199154<LocationMatch "/.+/">
    200155}}}
    … …  
    203158
    204159You can also use the same authentication realm for all of the projects using a `<LocationMatch>` directive:
    205 {{{
    206 #!xml
     160{{{#!apache
    207161<LocationMatch "/projects/[^/]+/login">
    208162  AuthType Basic
    … …  
    213167}}}
    214168
    215 == Virtual Host Configuration ==
    216 
    217 Below is the sample configuration required to set up your trac as a virtual server (i.e. when you access it at the URLs like
    218 !http://trac.mycompany.com):
    219 
    220 {{{
    221 #!xml
    222 <VirtualHost * >
     169=== Virtual Host Configuration
     170
     171Below is the sample configuration required to set up your Trac as a virtual server, ie when you access it at the URLs like
     172`http://trac.mycompany.com`:
     173
     174{{{#!apache
     175<VirtualHost *>
    223176    DocumentRoot /var/www/myproject
    224177    ServerName trac.mycompany.com
    … …  
    240193
    241194This does not seem to work in all cases. What you can do if it does not:
    242  * Try using `<LocationMatch>` instead of `<Location>`
    243  * <Location /> may, in your server setup, refer to the complete host instead of simple the root of the server. This means that everything (including the login directory referenced below) will be sent to python and authentication does not work (i.e. you get the infamous Authentication information missing error). If this applies to you, try using a sub-directory for trac instead of the root (i.e. /web/ and /web/login instead of / and /login).
     195 * Try using `<LocationMatch>` instead of `<Location>`.
     196 * `<Location />` may, in your server setup, refer to the complete host instead of simple the root of the server. This means that everything (including the login directory referenced below) will be sent to Python and authentication does not work, ie you get the infamous Authentication information missing error. If this is the case, try using a sub-directory for Trac instead of the root, ie /web/ and /web/login instead of / and /login.
    244197 * Depending on apache's `NameVirtualHost` configuration, you may need to use `<VirtualHost *:80>` instead of `<VirtualHost *>`.
    245198
    246 For a virtual host that supports multiple projects replace "`TracEnv`" /var/trac/myproject with "`TracEnvParentDir`" /var/trac/
    247 
    248 Note: !DocumentRoot should not point to your Trac project env. As Asmodai wrote on #trac: "suppose there's a webserver bug that allows disclosure of !DocumentRoot they could then leech the entire Trac environment".
    249 
    250 == Troubleshooting ==
    251 
    252 In general, if you get server error pages, you can either check the Apache error log, or enable the `PythonDebug` option:
    253 {{{
    254 #!xml
     199For a virtual host that supports multiple projects replace `TracEnv /var/trac/myproject` with `TracEnvParentDir /var/trac`.
     200
     201'''Note''': !DocumentRoot should not point to your Trac project env. As Asmodai wrote on #trac: "suppose there's a webserver bug that allows disclosure of !DocumentRoot they could then leech the entire Trac environment".
     202
     203== Troubleshooting
     204
     205If you get server error pages, you can either check the Apache error log, or enable the `PythonDebug` option:
     206{{{#!apache
    255207<Location /projects/myproject>
    256208  ...
    … …  
    261213For multiple projects, try restarting the server as well.
    262214
    263 === Expat-related segmentation faults === #expat
    264 
    265 This problem will most certainly hit you on Unix when using Python 2.4.
    266 In Python 2.4, some version of Expat (an XML parser library written in C) is used,
    267 and if Apache is using another version, this results in segmentation faults.
    268 As Trac 0.11 is using Genshi, which will indirectly use Expat, that problem
    269 can now hit you even if everything was working fine before with Trac 0.10.
    270 
    271 See Graham Dumpleton's detailed [http://www.dscpl.com.au/wiki/ModPython/Articles/ExpatCausingApacheCrash explanation and workarounds] for the issue.
    272 
    273 === Form submission problems ===
     215=== Login Not Working
     216
     217If you've used `<Location />` directive, it will override any other directives, as well as `<Location /login>`.
     218The workaround is to use negation expression as follows (for multi project setups):
     219{{{#!apache
     220#this one for other pages
     221<Location ~ "/*(?!login)">
     222   SetHandler mod_python
     223   PythonHandler trac.web.modpython_frontend
     224   PythonOption TracEnvParentDir /projects
     225   PythonOption TracUriRoot /
     226</Location>
     227
     228#this one for login page
     229<Location ~ "/[^/]+/login">
     230   SetHandler mod_python
     231   PythonHandler trac.web.modpython_frontend
     232   PythonOption TracEnvParentDir /projects
     233   PythonOption TracUriRoot /
     234
     235   #remove these if you don't want to force SSL
     236   RewriteEngine On
     237   RewriteCond %{HTTPS} off
     238   RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI}
     239
     240   AuthType Basic
     241   AuthName "Trac"
     242   AuthUserFile /projects/.htpasswd
     243   Require valid-user
     244</Location>
     245}}}
     246
     247=== Form submission problems
    274248
    275249If you're experiencing problems submitting some of the forms in Trac (a common problem is that you get redirected to the start page after submission), check whether your {{{DocumentRoot}}} contains a folder or file with the same path that you mapped the mod_python handler to. For some reason, mod_python gets confused when it is mapped to a location that also matches a static resource.
    276250
    277 === Problem with virtual host configuration ===
    278 
    279 If the <Location /> directive is used, setting the `DocumentRoot` may result in a ''403 (Forbidden)'' error. Either remove the `DocumentRoot` directive, or make sure that accessing the directory it points is allowed (in a corresponding `<Directory>` block).
    280 
    281 Using <Location /> together with `SetHandler` resulted in having everything handled by mod_python, which leads to not being able download any CSS or images/icons. I used <Location /trac> `SetHandler None` </Location> to circumvent the problem, though I do not know if this is the most elegant solution.
    282 
    283 === Using .htaccess ===
     251=== Problem with virtual host configuration
     252
     253If the <Location /> directive is used, setting the `DocumentRoot` may result in a ''403 (Forbidden)'' error. Either remove the `DocumentRoot` directive, or make sure that accessing the directory it points is allowed, in a corresponding `<Directory>` block.
     254
     255Using <Location /> together with `SetHandler` resulted in having everything handled by mod_python, which leads to not being able to download any CSS or images/icons. Use <Location /trac> `SetHandler None` </Location> to circumvent the problem, though this may not be the most elegant solution.
     256
     257=== Problem with zipped egg
     258
     259It's possible that your version of mod_python will not import modules from zipped eggs. If you encounter an `ImportError: No module named trac` in your Apache logs but you think everything is where it should be, this might be your problem. Look in your site-packages directory; if the Trac module appears as a ''file'' rather than a ''directory'', then this might be your problem. To rectify this, try installing Trac using the `--always-unzip` option:
     260
     261{{{#!sh
     262easy_install --always-unzip Trac-0.12b1.zip
     263}}}
     264
     265=== Using .htaccess
    284266
    285267Although it may seem trivial to rewrite the above configuration as a directory in your document root with a `.htaccess` file, this does not work. Apache will append a "/" to any Trac URLs, which interferes with its correct operation.
    286268
    287 It may be possible to work around this with mod_rewrite, but I failed to get this working. In all, it is more hassle than it is worth. Stick to the provided instructions. :)
    288 
    289 A success story: For me it worked out-of-box, with following trivial config:
    290 {{{
     269It may be possible to work around this with mod_rewrite, but I failed to get this working. In all, it is more hassle than it is worth.
     270
     271This also works out-of-box, with following trivial config:
     272{{{#!apache
    291273SetHandler mod_python
    292274PythonInterpreter main_interpreter
    293 PythonHandler trac.web.modpython_frontend 
     275PythonHandler trac.web.modpython_frontend
    294276PythonOption TracEnv /system/path/to/this/directory
    295277PythonOption TracUriRoot /path/on/apache
    … …  
    301283}}}
    302284
    303 The `TracUriRoot` is obviously the path you need to enter to the browser to get to the trac (e.g. domain.tld/projects/trac)
    304 
    305 === Additional .htaccess help ===
    306 
    307 If you are using the .htaccess method you may have additional problems if your trac directory is inheriting .htaccess directives from another. This may also help to add to your .htaccess file:
    308 
    309 {{{
     285The `TracUriRoot` is obviously the path you need to enter to the browser to get to Trac, eg `domain.tld/projects/trac`.
     286
     287=== Additional .htaccess help
     288
     289If you are using the .htaccess method you may have additional problems if your Trac directory is inheriting .htaccess directives from another. This may also help to add to your .htaccess file:
     290
     291{{{#!apache
    310292<IfModule mod_rewrite.c>
    311293  RewriteEngine Off
    … …  
    313295}}}
    314296
    315 
    316 === Win32 Issues ===
    317 If you run trac with mod_python < 3.2 on Windows, uploading attachments will '''not''' work. This problem is resolved in mod_python 3.1.4 or later, so please upgrade mod_python to fix this.
    318 
    319 
    320 === OS X issues ===
    321 
    322 When using mod_python on OS X you will not be able to restart Apache using `apachectl restart`. This is apparently fixed in mod_python 3.2, but there's also a patch available for earlier versions [http://www.dscpl.com.au/projects/vampire/patches.html here].
    323 
    324 === SELinux issues ===
    325 
    326 If Trac reports something like: ''Cannot get shared lock on db.lock''
    327 The security context on the repository may need to be set:
    328 
    329 {{{
     297=== Platform specific issues
     298==== Win32 Issues
     299
     300If you run Trac with mod_python < 3.2 on Windows, uploading attachments will '''not''' work. This problem is resolved in mod_python 3.1.4 or later, so please upgrade mod_python to fix this.
     301
     302==== OS X issues
     303
     304When using mod_python on OS X you will not be able to restart Apache using `apachectl restart`. This is apparently fixed in mod_python 3.2, so please upgrade mod_python to fix this.
     305
     306==== SELinux issues
     307
     308If Trac reports something like: `Cannot get shared lock on db.lock`, then the security context on the repository may need to be set:
     309
     310{{{#!sh
    330311chcon -R -h -t httpd_sys_content_t PATH_TO_REPOSITORY
    331312}}}
    332313
    333 See also [http://subversion.tigris.org/faq.html#reposperms]
    334 
    335 === FreeBSD issues ===
    336 Pay attention to the version of the installed mod_python and sqlite packages. Ports have both the new and old ones, but earlier versions of pysqlite and mod_python won't integrate as the former requires threaded support in python, and the latter requires a threadless install.
    337 
    338 If you compiled and installed apache2, apache wouldn´t support threads (cause it doesn´t work very well on FreeBSD). You could force thread support when running ./configure for apache, using --enable-threads, but this isn´t recommendable.
    339 The best option [http://modpython.org/pipermail/mod_python/2006-September/021983.html seems to be] adding to /usr/local/apache2/bin/ennvars the line
    340 
    341 {{{
     314See also [https://subversion.apache.org/faq.html#reposperms How do I set repository permissions correctly?]
     315
     316==== FreeBSD issues
     317
     318The FreeBSD ports have both the new and old versions of mod_python and SQLite, but earlier versions of pysqlite and mod_python won't integrate:
     319 * pysqlite requires threaded support in Python
     320 * mod_python requires a threadless install.
     321
     322Apache2 does not automatically support threads on FreeBSD. You could force thread support when running `./configure` for Apache, using `--enable-threads`, but this isn´t recommended.
     323The best option [http://modpython.org/pipermail/mod_python/2006-September/021983.html seems to be] adding to /usr/local/apache2/bin/ennvars the line:
     324
     325{{{#!sh
    342326export LD_PRELOAD=/usr/lib/libc_r.so
    343327}}}
    344328
    345 === Subversion issues ===
    346 
    347 If you get the following Trac Error `Unsupported version control system "svn"` only under mod_python, though it works well on the command-line and even with TracStandalone, chances are that you forgot to add the path to the Python bindings with the [TracModPython#ConfiguringPythonPath PythonPath] directive. (The better way is to add a link to the bindings in the Python `site-packages` directory, or create a `.pth` file in that directory.)
    348 
    349 If this is not the case, it's possible that you're using Subversion libraries that are binary incompatible with the apache ones (an incompatibility of the `apr` libraries is usually the cause). In that case, you also won't be able to use the svn modules for Apache (`mod_dav_svn`).
    350 
    351 You also need a recent version of `mod_python` in order to avoid a runtime error ({{{argument number 2: a 'apr_pool_t *' is expected}}}) due to the default usage of multiple sub-interpreters. 3.2.8 ''should'' work, though it's probably better to use the workaround described in [trac:#3371 #3371], in order to force the use of the main interpreter:
    352 {{{
     329==== Fedora 7 Issues
     330
     331Make sure you install the 'python-sqlite2' package as it seems to be required for TracModPython, but not for tracd.
     332
     333=== Subversion issues
     334
     335If you get the following Trac error `Unsupported version control system "svn"` only under mod_python, though it works well on the command-line and even with TracStandalone, chances are that you forgot to add the path to the Python bindings with the [TracModPython#ConfiguringPythonPath PythonPath] directive. A better way is to add a link to the bindings in the Python `site-packages` directory, or create a `.pth` file in that directory.
     336
     337If this is not the case, it's possible that you are using Subversion libraries that are binary incompatible with the Apache ones and an incompatibility of the `apr` libraries is usually the cause. In that case, you also won't be able to use the svn modules for Apache (`mod_dav_svn`).
     338
     339You also need a recent version of `mod_python` in order to avoid a runtime error ({{{argument number 2: a 'apr_pool_t *' is expected}}}) due to the default usage of multiple sub-interpreters. Version 3.2.8 ''should'' work, though it's probably better to use the workaround described in [trac:#3371 #3371], in order to force the use of the main interpreter:
     340{{{#!apache
    353341PythonInterpreter main_interpreter
    354342}}}
    355 This is anyway the recommended workaround for other well-known issues seen when using the Python bindings for Subversion within mod_python ([trac:#2611 #2611], [trac:#3455 #3455]). See in particular Graham Dumpleton's comment in [trac:comment:9:ticket:3455 #3455] explaining the issue.
    356 
    357 === Page layout issues ===
    358 
    359 If the formatting of the Trac pages look weird chances are that the style sheets governing the page layout are not handled properly by the web server. Try adding the following lines to your apache configuration:
    360 {{{
    361 #!xml
     343
     344This is also the recommended workaround for other issues seen when using the Python bindings for Subversion within mod_python ([trac:#2611 #2611], [trac:#3455 #3455]). See in particular Graham Dumpleton's comment in [trac:comment:9:ticket:3455 #3455] explaining the issue.
     345
     346=== Page layout issues
     347
     348If the formatting of the Trac pages look weird, chances are that the style sheets governing the page layout are not handled properly by the web server. Try adding the following lines to your Apache configuration:
     349{{{#!apache
    362350Alias /myproject/css "/usr/share/trac/htdocs/css"
    363351<Location /myproject/css>
    … …  
    366354}}}
    367355
    368 Note: For the above configuration to have any effect it must be put after the configuration of your project root location, i.e. {{{<Location /myproject />}}}.
    369 
    370 === HTTPS issues ===
    371 
    372 If you want to run Trac fully under https you might find that it tries to redirect to plain http. In this case just add the following line to your apache configuration:
    373 {{{
    374 #!xml
    375 <VirtualHost * >
     356'''Note''': For the above configuration to have any effect it must be put after the configuration of your project root location, ie {{{<Location /myproject />}}}.
     357
     358=== HTTPS issues
     359
     360If you want to run Trac fully under https you might find that it tries to redirect to plain http. In this case just add the following line to your Apache configuration:
     361{{{#!apache
     362<VirtualHost *>
    376363    DocumentRoot /var/www/myproject
    377364    ServerName trac.mycompany.com
    … …  
    381368}}}
    382369
    383 === Fedora 7 Issues ===
    384 Make sure you install the 'python-sqlite2' package as it seems to be required for TracModPython but not for tracd
    385 
    386 
    387 === Segmentation fault with php5-mhash or other php5 modules ===
    388 You may encounter segfaults (reported on debian etch) if php5-mhash module is installed. Try to remove it to see if this solves the problem. See debian bug report [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=411487]
    389 
    390 Some people also have troubles when using php5 compiled with its own 3rd party libraries instead of system libraries. Check here [http://www.djangoproject.com/documentation/modpython/#if-you-get-a-segmentation-fault]
     370=== Segmentation fault with php5-mhash or other php5 modules
     371
     372You may encounter segfaults (reported on Debian etch) if php5-mhash module is installed. Try to remove it to see if this solves the problem. See [https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=411487 Debian bug report].
     373
     374Some people also have troubles when using PHP5 compiled with its own third party libraries instead of system libraries. Check [https://www.djangoproject.com/documentation/modpython/#if-you-get-a-segmentation-fault Django segmentation fault].
    391375
    392376----
    393 See also:  TracGuide, TracInstall, [wiki:TracModWSGI ModWSGI], [wiki:TracFastCgi FastCGI], [wiki:TracModPython ModPython], [trac:TracNginxRecipe TracNginxRecipe]
     377See also: TracGuide, TracInstall, [wiki:TracModWSGI ModWSGI], [wiki:TracFastCgi FastCGI], [trac:TracNginxRecipe]