Changes between Version 1 and Version 2 of TracModPython
- Timestamp:
- 2007-12-19T17:55:53Z (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracModPython
v1 v2 4 4 Trac 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. 5 5 6 These instructions are for Apache 2; if you are still using Apache 1.3, you may have some luck with [wiki:TracModPython2.7 TracModPython2.7]. 7 6 8 == Simple configuration == 7 9 … … 12 14 13 15 ''Note: The exact path to the module depends on how the HTTPD installation is laid out.'' 14 15 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. 16 {{{ 16 On Debian using apt-get 17 {{{ 18 apt-get install libapache2-mod-python libapache2-mod-python-doc 19 }}} 20 (Still on Debian) after you have installed mod_python, you must enable the modules in apache2 (equivalent of the above Load Module directive): 21 {{{ 22 a2enmod mod_python 23 }}} 24 On Fedora use, using yum: 25 {{{ 26 yum install mod_python 27 }}} 28 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+. 29 {{{ 30 #!xml 17 31 <Location /mpinfo> 18 32 SetHandler mod_python 33 PythonInterpreter main_interpreter 19 34 PythonHandler mod_python.testhandler 20 35 </Location> … … 23 38 A simple setup of Trac on mod_python looks like this: 24 39 {{{ 40 #!xml 25 41 <Location /projects/myproject> 26 42 SetHandler mod_python 43 PythonInterpreter main_interpreter 27 44 PythonHandler trac.web.modpython_frontend 28 45 PythonOption TracEnv /var/trac/myproject … … 31 48 }}} 32 49 33 The option '''`TracUriRoot`''' may or may not be necessary in your setup. Try your configuration with out it, and if the URLs produced by Trac look wrong or if Trac does not seem to recognize the URLs correctly, add the '''`TracUriRoot`''' option. You will notice that the `Location` and '''`TracUriRoot`''' have the same path.50 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. 34 51 35 52 === Configuring Authentication === 36 53 37 Configuring authentication works just like for [wiki:TracCgi#AddingAuthentication CGI]: 38 {{{ 39 <Location "/projects/myproject/login"> 54 Creating password files and configuring authentication works similar to the process for [wiki:TracCgi#AddingAuthentication CGI]: 55 {{{ 56 #!xml 57 <Location /projects/myproject/login> 40 58 AuthType Basic 41 59 AuthName "myproject" … … 45 63 }}} 46 64 65 Configuration for mod_ldap authentication in Apache is a bit tricky (httpd 2.2.x and OpenLDAP: slapd 2.3.19) 66 67 1. You need to load the following modules in Apache httpd.conf 68 {{{ 69 LoadModule ldap_module modules/mod_ldap.so 70 LoadModule authnz_ldap_module modules/mod_authnz_ldap.so 71 }}} 72 73 2. Your httpd.conf also needs to look something like: 74 75 {{{ 76 #!xml 77 <Location /trac/> 78 SetHandler mod_python 79 PythonInterpreter main_interpreter 80 PythonHandler trac.web.modpython_frontend 81 PythonOption TracEnv /home/trac/ 82 PythonOption TracUriRoot /trac/ 83 Order deny,allow 84 Deny from all 85 Allow from 192.168.11.0/24 86 AuthType Basic 87 AuthName "Trac" 88 AuthBasicProvider "ldap" 89 AuthLDAPURL "ldap://127.0.0.1/dc=example,dc=co,dc=ke?uid?sub?(objectClass=inetOrgPerson)" 90 authzldapauthoritative Off 91 require valid-user 92 </Location> 93 }}} 94 95 Or the LDAP interface to a Microsoft Active Directory: 96 97 {{{ 98 #!xml 99 <Location /trac/> 100 SetHandler mod_python 101 PythonInterpreter main_interpreter 102 PythonHandler trac.web.modpython_frontend 103 PythonOption TracEnv /home/trac/ 104 PythonOption TracUriRoot /trac/ 105 Order deny,allow 106 Deny from all 107 Allow from 192.168.11.0/24 108 AuthType Basic 109 AuthName "Trac" 110 AuthBasicProvider "ldap" 111 AuthLDAPURL "ldap://adserver.company.com:3268/DC=company,DC=com?sAMAccountName?sub?(objectClass=user)" 112 AuthLDAPBindDN ldap-auth-user@company.com 113 AuthLDAPBindPassword "the_password" 114 authzldapauthoritative Off 115 # require valid-user 116 require ldap-group CN=Trac Users,CN=Users,DC=company,DC=com 117 </Location> 118 }}} 119 120 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. 121 122 Note 2: Active Directory requires an authenticating user/password to access records (AuthLDAPBindDN and AuthLDAPBindPassword). 123 124 Note 3: The directive "require ldap-group ..." specifies an AD group whose members are allowed access. 125 126 127 47 128 === Setting the !PythonPath === 48 129 49 130 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: 50 131 {{{ 132 #!xml 51 133 <Location /projects/myproject> 52 134 ... … … 62 144 The Trac mod_python handler supports a configuration option similar to Subversion's `SvnParentPath`, called `TracEnvParentDir`: 63 145 {{{ 146 #!xml 64 147 <Location /projects> 65 148 SetHandler mod_python 149 PythonInterpreter main_interpreter 66 150 PythonHandler trac.web.modpython_frontend 67 151 PythonOption TracEnvParentDir /var/trac … … 74 158 If you don't want to have the subdirectory listing as your projects home page you can use a 75 159 {{{ 160 #!xml 76 161 <LocationMatch "/.+/"> 77 162 }}} … … 81 166 You can also use the same authentication realm for all of the projects using a `<LocationMatch>` directive: 82 167 {{{ 168 #!xml 83 169 <LocationMatch "/projects/[^/]+/login"> 84 170 AuthType Basic … … 95 181 96 182 {{{ 183 #!xml 97 184 <VirtualHost * > 98 DocumentRoot /var/ trac/myproject185 DocumentRoot /var/www/myproject 99 186 ServerName trac.mycompany.com 100 187 <Location /> 101 188 SetHandler mod_python 189 PythonInterpreter main_interpreter 102 190 PythonHandler trac.web.modpython_frontend 103 191 PythonOption TracEnv /var/trac/myproject … … 113 201 }}} 114 202 203 if you have issues with login try using `<LocationMatch>` instead of `<Location>` 204 115 205 For a virtual host that supports multiple projects replace "`TracEnv`" /var/trac/myproject with "`TracEnvParentDir`" /var/trac/ 116 206 … … 119 209 In general, if you get server error pages, you can either check the Apache error log, or enable the `PythonDebug` option: 120 210 {{{ 211 #!xml 121 212 <Location /projects/myproject> 122 213 ... … … 125 216 }}} 126 217 218 For multiple projects, try restarting the server as well. 219 220 === Expat-related segmentation faults === #expat 221 222 This problem will most certainly hit you on Unix when using python 2.4. 223 In Python 2.4, some version of Expat (an XML parser library written in C) is used, 224 and if Apache is using another version, this results in segmentation faults. 225 As Trac 0.11 is using Genshi, which will use indirectly use Expat, that problem 226 can now hit you even if everything was working fine before with Trac 0.10. 227 228 See Graham Dumpleton's detailed [http://www.dscpl.com.au/wiki/ModPython/Articles/ExpatCausingApacheCrash explanation and workarounds] for the issue. 229 127 230 === Form submission problems === 128 231 … … 144 247 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. 145 248 249 146 250 === OS X issues === 147 251 … … 162 266 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. 163 267 268 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 recomendable. 269 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 270 271 {{{ 272 export LD_PRELOAD=/usr/lib/libc_r.so 273 }}} 274 164 275 === Subversion issues === 165 276 … … 167 278 168 279 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`). 280 281 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 #3371, in order to force the use of the main interpreter: 282 {{{ 283 PythonInterpreter main_interpreter 284 }}} 285 This is anyway the recommended workaround for other well-known issues seen when using the Python bindings for Subversion within mod_python (#2611, #3455). See in particular Graham Dumpleton's comment in [comment:ticket:3455:9 #3455] explaining the issue. 286 287 === Page layout issues === 288 289 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: 290 {{{ 291 #!xml 292 Alias /myproject/css "/usr/share/trac/htdocs/css" 293 <Location /myproject/css> 294 SetHandler None 295 </Location> 296 }}} 297 298 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 />}}}. 299 300 === HTTPS issues === 301 302 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: 303 {{{ 304 #!xml 305 <VirtualHost * > 306 DocumentRoot /var/www/myproject 307 ServerName trac.mycompany.com 308 SetEnv HTTPS 1 309 .... 310 </VirtualHost> 311 }}} 312 313 === Fedora 7 Issues === 314 Make sure you install the 'python-sqlite2' package as it seems to be required for TracModPython but not for tracd 315 316 317 === Segmentation fault with php5-mhash or other php5 modules === 318 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]] 319 320 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]] 169 321 170 322 ----