Changes between Version 1 and Version 2 of TracModPython
- Timestamp:
- 09/25/06 21:09:57 (18 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracModPython
v1 v2 1 1 = Trac and mod_python = 2 [[TracGuideToc]] 2 3 3 Trac supports [http://www.modpython.org/ mod_python], which speeds up Trac's response times considerably and permits use of many Apache features not possible with [wiki:TracStandalone tracd]/mod_proxy.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. 4 5 5 6 == Simple configuration == … … 8 9 {{{ 9 10 LoadModule python_module modules/mod_python.so 11 }}} 12 13 ''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 {{{ 17 <Location /mpinfo> 18 SetHandler mod_python 19 PythonHandler mod_python.testhandler 20 </Location> 10 21 }}} 11 22 … … 20 31 }}} 21 32 22 Note that the option `TracUriRoot` may or may not be necessary in your setup. Try without first, and if the URLs produced by Trac look wrong or if Trac does not seem to recognize the URLs correctly, add the `TracUriRoot` option.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. 23 34 24 Configuring authentication works the same as for [wiki:TracCgi#AddingAuthentication CGI]: 35 === Configuring Authentication === 36 37 Configuring authentication works just like for [wiki:TracCgi#AddingAuthentication CGI]: 25 38 {{{ 26 39 <Location "/projects/myproject/login"> 27 40 AuthType Basic 28 41 AuthName "myproject" 29 AuthUserFile /var/trac/myproject/.ht access42 AuthUserFile /var/trac/myproject/.htpasswd 30 43 Require valid-user 31 44 </Location> 32 45 }}} 46 47 === Setting the !PythonPath === 33 48 34 49 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: … … 41 56 }}} 42 57 58 Be careful about using the !PythonPath directive, and ''not'' `SetEnv PYTHONPATH`, as the latter won't work. 43 59 44 60 == Setting up multiple projects == 45 61 46 The Trac mod_python handler handlersupports a configuration option similar to Subversion's `SvnParentPath`, called `TracEnvParentDir`:62 The Trac mod_python handler supports a configuration option similar to Subversion's `SvnParentPath`, called `TracEnvParentDir`: 47 63 {{{ 48 64 <Location /projects> … … 54 70 }}} 55 71 56 When you request the `/projects` URL, you will get a listing of all subdirectories of the directory you set as `TracEnvParentDir` . Selecting any project in the list will bring you to the corresponding Trac environment.72 When 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. 57 73 58 74 If you don't want to have the subdirectory listing as your projects home page you can use a … … 65 81 You can also use the same authentication realm for all of the projects using a `<LocationMatch>` directive: 66 82 {{{ 67 <LocationMatch "/ [^/]+/login">83 <LocationMatch "/projects/[^/]+/login"> 68 84 AuthType Basic 69 85 AuthName "Trac" 70 AuthUserFile /var/trac/.ht access86 AuthUserFile /var/trac/.htpasswd 71 87 Require valid-user 72 88 </LocationMatch> … … 82 98 DocumentRoot /var/trac/myproject 83 99 ServerName trac.mycompany.com 84 < Directory/>100 <Location /> 85 101 SetHandler mod_python 86 102 PythonHandler trac.web.modpython_frontend 87 103 PythonOption TracEnv /var/trac/myproject 88 104 PythonOption TracUriRoot / 89 </ Directory>105 </Location> 90 106 <Location /login> 91 107 AuthType Basic 92 108 AuthName "MyCompany Trac Server" 93 AuthUserFile /var/trac/myproject/.ht users109 AuthUserFile /var/trac/myproject/.htpasswd 94 110 Require valid-user 95 111 </Location> … … 97 113 }}} 98 114 115 For a virtual host that supports multiple projects replace "`TracEnv`" /var/trac/myproject with "`TracEnvParentDir`" /var/trac/ 116 99 117 == Troubleshooting == 118 119 In general, if you get server error pages, you can either check the Apache error log, or enable the `PythonDebug` option: 120 {{{ 121 <Location /projects/myproject> 122 ... 123 PythonDebug on 124 </Location> 125 }}} 100 126 101 127 === Form submission problems === 102 128 103 129 If 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. 130 131 === Problem with virtual host configuration === 132 133 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). 134 135 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. 104 136 105 137 === Using .htaccess === … … 110 142 111 143 === Win32 Issues === 112 113 If you run trac with mod_python (3.1.3 or 3.1.4) on Windows, 114 uploading attachments will '''not''' work. 115 This is a known problem which we can't solve cleanly at the Trac level. 116 117 However, there is a workaround for this at the mod_python level, 118 which is to apply the following patch [http://projects.edgewall.com/trac/attachment/ticket/554/util_py.patch attachment:ticket:554:util_py.patch] 119 to the (Lib/site-packages)/modpython/util.py file. 120 121 If you don't have the `patch` command, that file can be replaced with the [http://svn.apache.org/viewcvs.cgi/httpd/mod_python/trunk/lib/python/mod_python/util.py?rev=103562&view=markup fixed util.py] (fix which, although done prior to the 3.1.4 release, is ''not'' 122 present in 3.1.4). 144 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. 123 145 124 146 === OS X issues === … … 126 148 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]. 127 149 150 === SELinux issues === 151 152 If Trac reports something like: ''Cannot get shared lock on db.lock'' 153 The security context on the repository may need to be set: 154 155 {{{ 156 chcon -R -h -t httpd_sys_content_t PATH_TO_REPOSITORY 157 }}} 158 159 See also [[http://subversion.tigris.org/faq.html#reposperms]] 160 161 === FreeBSD issues === 162 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 164 === Subversion issues === 165 166 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.) 167 168 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`). 169 128 170 ---- 129 171 See also TracGuide, TracInstall, TracCgi, TracFastCgi