Changes between Version 61 and Version 62 of TracModWSGI
- Timestamp:
- Jan 3, 2015, 12:52:32 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracModWSGI
v61 v62 1 1 = Trac and mod_wsgi = 2 2 3 4 3 [http://code.google.com/p/modwsgi/ mod_wsgi] is an Apache module for running WSGI-compatible Python applications directly on top of the Apache webserver. The mod_wsgi adapter is written completely in C and provides very good performance. 5 4 … … 8 7 == The `trac.wsgi` script 9 8 10 Trac can be run on top of mod_wsgi with the help of the following application script, which is just a Python file, though usually saved with a `.wsgi` extension ).9 Trac can be run on top of mod_wsgi with the help of the following application script, which is just a Python file, though usually saved with a `.wsgi` extension. 11 10 12 11 === A very basic script … … 23 22 }}} 24 23 25 The `TRAC_ENV` variable should naturally be the directory for your Trac environment (if you have several Trac environments in a directory, you can also use `TRAC_ENV_PARENT_DIR` instead), while the `PYTHON_EGG_CACHE` should be a directory where Python can temporarily extract Python eggs.24 The `TRAC_ENV` variable should naturally be the directory for your Trac environment, and the `PYTHON_EGG_CACHE` should be a directory where Python can temporarily extract Python eggs. If you have several Trac environments in a directory, you can also use `TRAC_ENV_PARENT_DIR` instead of `TRAC_ENV`. 26 25 27 26 On Windows: … … 30 29 os.environ['PYTHON_EGG_CACHE'] = r'C:\Users\Administrator\AppData\Roaming\Python-Eggs' 31 30 }}} 32 - If run under a Window service, you should create a directory for Python Egg cache .31 - If run under a Window service, you should create a directory for Python Egg cache: 33 32 {{{#!python 34 33 os.environ['PYTHON_EGG_CACHE'] = r'C:\Trac-Python-Eggs' … … 37 36 === A more elaborate script 38 37 39 If you 're using multiple `.wsgi` files (for example one per Trac environment) you must ''not'' use `os.environ['TRAC_ENV']` to set the path to the Trac environment. Using this method may lead to Trac delivering the content of another Trac environment, as the variable may be filled with the path of a previously viewed Trac environment.38 If you are using multiple `.wsgi` files (for example one per Trac environment) you must ''not'' use `os.environ['TRAC_ENV']` to set the path to the Trac environment. Using this method may lead to Trac delivering the content of another Trac environment, as the variable may be filled with the path of a previously viewed Trac environment. 40 39 41 40 To solve this problem, use the following `.wsgi` file instead: … … 53 52 For clarity, you should give this file a `.wsgi` extension. You should probably put the file in its own directory, since you will expose it to Apache. 54 53 55 If you have installed Trac and eggs in a path different from the standard oneyou should add that path by adding the following code at the top of the wsgi script:54 If you have installed Trac and Python eggs in a path different from the standard one, you should add that path by adding the following code at the top of the wsgi script: 56 55 57 56 {{{#!python … … 64 63 === Recommended `trac.wsgi` script 65 64 66 A somewhat robust and generic version of this file can be created using the `trac-admin <env> deploy <dir>` command which automatically substitutes the required paths (see TracInstall#cgi-bin).67 68 If you 're using Trac with multiple projectsyou can specify their common parent directory using the `TRAC_ENV_PARENT_DIR` in the trac.wsgi in trac.wsgi: ''65 A somewhat robust and generic version of this file can be created using the `trac-admin <env> deploy <dir>` command which automatically substitutes the required paths, see TracInstall#cgi-bin. 66 67 If you are using Trac with multiple projects, you can specify their common parent directory using the `TRAC_ENV_PARENT_DIR` in the trac.wsgi in trac.wsgi: '' 69 68 70 69 {{{#!python … … 78 77 == Mapping requests to the script 79 78 80 After you've done preparing your .wsgi script, add the following to your Apache configuration file (`httpd.conf` for example).79 After preparing your .wsgi script, add the following to your Apache configuration file, typically `httpd.conf`: 81 80 82 81 {{{ … … 104 103 }}} 105 104 106 In order to let Apache run the script, access to the directory in which the script resides is opened up to all of Apache. Additionally, the `WSGIApplicationGroup` directive ensures that Trac is always run in the first Python interpreter created by mod_wsgi ; this is necessary because the Subversion Python bindings, which are used by Trac, don't always work in other sub-interpreters and may cause requests to hang or cause Apache to crash as a result. After adding this configuration, restart Apache, and then it should work.105 In order to let Apache run the script, access to the directory in which the script resides is opened up to all of Apache. Additionally, the `WSGIApplicationGroup` directive ensures that Trac is always run in the first Python interpreter created by mod_wsgi. This is necessary because the Subversion Python bindings, which are used by Trac, don't always work in other sub-interpreters and may cause requests to hang or cause Apache to crash. After adding this configuration, restart Apache, and then it should work. 107 106 108 107 To test the setup of Apache, mod_wsgi and Python itself (ie. without involving Trac and dependencies), this simple wsgi application can be used to make sure that requests gets served (use as only content in your `.wsgi` script): … … 116 115 For more information about using the mod_wsgi specific directives, see the [http://code.google.com/p/modwsgi/wiki/ mod_wsgi's wiki] and more specifically the [http://code.google.com/p/modwsgi/wiki/IntegrationWithTrac IntegrationWithTrac] page. 117 116 118 119 117 == Configuring Authentication 120 118 121 We describe in the the following sections different methods for setting up authentication. 122 123 See also [http://httpd.apache.org/docs/2.2/howto/auth.html Authentication, Authorization and Access Control] in the Apache guide. 119 The following sections describe different methods for setting up authentication. See also [http://httpd.apache.org/docs/2.2/howto/auth.html Authentication, Authorization and Access Control] in the Apache guide. 124 120 125 121 === Using Basic Authentication === 126 122 127 The simplest way to enable authentication with Apache is to create a password file. Use the `htpasswd` program to create the password file:123 The simplest way to enable authentication with Apache is to create a password file. Use the `htpasswd` program as follows: 128 124 {{{ 129 125 $ htpasswd -c /somewhere/trac.htpasswd admin … … 133 129 }}} 134 130 135 After the first user, you don t need the "-c" option anymore:131 After the first user, you don't need the "-c" option anymore: 136 132 {{{ 137 133 $ htpasswd /somewhere/trac.htpasswd john … … 145 141 After you've created the users, you can set their permissions using TracPermissions. 146 142 147 Now, you 'llneed to enable authentication against the password file in the Apache configuration:143 Now, you need to enable authentication against the password file in the Apache configuration: 148 144 {{{ 149 145 <Location "/trac/login"> … … 155 151 }}} 156 152 157 If you 're hosting multiple projectsyou can use the same password file for all of them:153 If you are hosting multiple projects, you can use the same password file for all of them: 158 154 {{{ 159 155 <LocationMatch "/trac/[^/]+/login"> … … 171 167 For better security, it is recommended that you either enable SSL or at least use the “digest” authentication scheme instead of “Basic”. 172 168 173 You 'llhave to create your `.htpasswd` file with the `htdigest` command instead of `htpasswd`, as follows:169 You have to create your `.htpasswd` file with the `htdigest` command instead of `htpasswd`, as follows: 174 170 {{{ 175 171 # htdigest -c /somewhere/trac.htpasswd trac admin … … 198 194 }}} 199 195 200 201 196 See also the [http://httpd.apache.org/docs/2.2/mod/mod_auth_digest.html mod_auth_digest] documentation. 202 197 203 198 === Using LDAP Authentication 204 199 205 Configuration for [http://httpd.apache.org/docs/2.2/mod/mod_ldap.html mod_ldap] authentication in Apache is a bit tricky (httpd 2.2.x and OpenLDAP: slapd 2.3.19)206 207 1. You need to load the following modules in Apache httpd.conf 200 Configuration for [http://httpd.apache.org/docs/2.2/mod/mod_ldap.html mod_ldap] authentication in Apache is more involved (httpd 2.2.x and OpenLDAP: slapd 2.3.19). 201 202 1. You need to load the following modules in Apache httpd.conf: 208 203 {{{ 209 204 LoadModule ldap_module modules/mod_ldap.so … … 228 223 }}} 229 224 230 231 225 3. You can use the LDAP interface as a way to authenticate to a Microsoft Active Directory: 232 226 233 234 227 Use the following as your LDAP URL: 235 228 {{{ … … 237 230 }}} 238 231 239 You will also need to provide an account for Apache to use when checking 240 credentials. As this password will be listed in plaintext in the 241 config, you should be sure to use an account specifically for this task: 232 You will also need to provide an account for Apache to use when checking credentials. As this password will be listed in plaintext in the config, you need to use an account specifically for this task: 242 233 {{{ 243 234 AuthLDAPBindDN ldap-auth-user@example.com … … 264 255 }}} 265 256 266 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. 267 268 Note 2: You can also require the user be a member of a certain LDAP group, instead of 269 just having a valid login: 257 Note 1: This is the case where the LDAP search will get around the multiple OUs, conecting to the Global Catalog Server portion of AD. Note 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. 258 259 Note 2: You can also require the user be a member of a certain LDAP group, instead of just having a valid login: 270 260 {{{ 271 261 Require ldap-group CN=Trac Users,CN=Users,DC=example,DC=com … … 273 263 274 264 See also: 275 - [http://httpd.apache.org/docs/2.2/mod/mod_authnz_ldap.html mod_authnz_ldap], documentation for mod_authnz_ldap 276 265 - [http://httpd.apache.org/docs/2.2/mod/mod_authnz_ldap.html mod_authnz_ldap], documentation for mod_authnz_ldap. 277 266 - [http://httpd.apache.org/docs/2.2/mod/mod_ldap.html mod_ldap], documentation for mod_ldap, which provides connection pooling and a shared cache. 278 267 - [http://trac-hacks.org/wiki/LdapPlugin TracHacks:LdapPlugin] for storing TracPermissions in LDAP. … … 280 269 === Using SSPI Authentication 281 270 282 If you are using Apache on Windows, you can use mod_auth_sspi to provide 283 single-sign-on. Download the module from the !SourceForge [http://sourceforge.net/projects/mod-auth-sspi/ mod-auth-sspi project] and then add the 284 following to your !VirtualHost: 271 If you are using Apache on Windows, you can use mod_auth_sspi to provide single-sign-on. Download the module from the !SourceForge [http://sourceforge.net/projects/mod-auth-sspi/ mod-auth-sspi project] and then add the following to your !VirtualHost: 285 272 {{{ 286 273 <Location /trac/login> … … 297 284 }}} 298 285 299 Using the above, usernames in Trac will be of the form `DOMAIN\username`, so 300 you may have to re-add permissions and such. If you do not want the domain to 301 be part of the username, set `SSPIOmitDomain On` instead. 286 Using the above, usernames in Trac will be of the form `DOMAIN\username`, so you may have to re-add permissions and such. If you do not want the domain to be part of the username, set `SSPIOmitDomain On` instead. 302 287 303 288 Some common problems with SSPI authentication: [trac:#1055], [trac:#1168] and [trac:#3338]. … … 333 318 === Example: Apache/mod_wsgi with Basic Authentication, Trac being at the root of a virtual host 334 319 335 Per the mod_wsgi documentation linked to above, here is an example Apache configuration that a) serves the Trac instance from a virtualhost subdomain and b) uses Apache basic authentication for Trac authentication. 336 320 Per the mod_wsgi documentation linked to above, here is an example Apache configuration that: 321 - serves the Trac instance from a virtualhost subdomain 322 - uses Apache basic authentication for Trac authentication. 337 323 338 324 If you want your Trac to be served from e.g. !http://trac.my-proj.my-site.org, then from the folder e.g. `/home/trac-for-my-proj`, if you used the command `trac-admin the-env initenv` to create a folder `the-env`, and you used `trac-admin the-env deploy the-deploy` to create a folder `the-deploy`, then first: … … 345 331 htpasswd htpasswd seconduser 346 332 }}} 347 (keep the file above your document root for security reasons) 348 349 Create this file e.g. (ubuntu) `/etc/apache2/sites-enabled/trac.my-proj.my-site.org.conf` with the following content s:333 Keep the file above your document root for security reasons. 334 335 Create this file e.g. (ubuntu) `/etc/apache2/sites-enabled/trac.my-proj.my-site.org.conf` with the following content: 350 336 351 337 {{{ … … 372 358 Note: for subdomains to work you would probably also need to alter `/etc/hosts` and add A-Records to your host's DNS. 373 359 374 375 360 == Troubleshooting 376 361 377 362 === Use a recent version 378 363 379 Please use either version 1.6, 2.4 or later of `mod_wsgi`. Versions prior to 2.4 in the 2.X branch have problems with some Apache configurations that use WSGI file wrapper extension. This extension is used in Trac to serve up attachments and static media files such as style sheets. If you are affected by this problem attachments will appear to be empty and formatting of HTML pages will appear not to work due to style sheet files not loading properly. Another frequent symptom is that binary attachment downloads are truncated. See mod_wsgi tickets [http://code.google.com/p/modwsgi/issues/detail?id=100 #100] and [http://code.google.com/p/modwsgi/issues/detail?id=132 #132].364 Please use either version 1.6, 2.4 or later of `mod_wsgi`. Versions prior to 2.4 in the 2.X branch have problems with some Apache configurations that use WSGI file wrapper extension. This extension is used in Trac to serve up attachments and static media files such as style sheets. If you are affected by this problem, attachments will appear to be empty and formatting of HTML pages will appear not to work due to style sheet files not loading properly. Another frequent symptom is that binary attachment downloads are truncated. See mod_wsgi tickets [http://code.google.com/p/modwsgi/issues/detail?id=100 #100] and [http://code.google.com/p/modwsgi/issues/detail?id=132 #132]. 380 365 381 366 ''Note: using mod_wsgi 2.5 and Python 2.6.1 gave an Internal Server Error on my system (Apache 2.2.11 and Trac 0.11.2.1). Upgrading to Python 2.6.2 (as suggested [http://www.mail-archive.com/modwsgi@googlegroups.com/msg01917.html here]) solved this for me[[BR]]-- Graham Shanks'' 382 367 383 If you plan to use `mod_wsgi` in embedded mode on Windows or with the MPM worker on Linux, then you 'll even need version 0.3.4 or greater (see [trac:#10675] for details).368 If you plan to use `mod_wsgi` in embedded mode on Windows or with the MPM worker on Linux, then you will need version 0.3.4 or greater. See [trac:#10675] for details. 384 369 385 370 === Getting Trac to work nicely with SSPI and 'Require Group' === 386 If like me you've set Trac up on Apache, Win32 and configured SSPI, but added a 'Require group' option to your apache configuration, then the SSPIOmitDomain option is probably not working. If its not working your usernames in trac are probably looking like 'DOMAIN\user' rather than 'user'. 387 388 This WSGI script 'fixes' things, hope it helps: 371 372 If you have set Trac up on Apache, Win32 and configured SSPI, but added a 'Require group' option to your apache configuration, then the SSPIOmitDomain option is probably not working. If it is not working, your usernames in Trac probably look like 'DOMAIN\user' rather than 'user'. 373 374 This WSGI script 'fixes' that: 389 375 {{{#!python 390 376 import os … … 400 386 }}} 401 387 402 403 388 === Trac with PostgreSQL === 404 389 405 When using the mod_wsgi adapter with multiple Trac instances and PostgreSQL (or MySQL?) as a database back-end, the server ''may'' create a lot of open database connections and thus PostgreSQL processes.406 407 A somewhat brutal workaround is to disable dconnection pooling in Trac. This is done by setting `poolable = False` in `trac.db.postgres_backend` on the `PostgreSQLConnection` class.408 409 But it 's not necessary to edit the source of Trac, the following lines in `trac.wsgi` will also work:390 When using the mod_wsgi adapter with multiple Trac instances and PostgreSQL (or MySQL?) as the database, the server ''may'' create a lot of open database connections and thus PostgreSQL processes. 391 392 A somewhat brutal workaround is to disable connection pooling in Trac. This is done by setting `poolable = False` in `trac.db.postgres_backend` on the `PostgreSQLConnection` class. 393 394 But it is not necessary to edit the source of Trac. The following lines in `trac.wsgi` will also work: 410 395 411 396 {{{#!python … … 421 406 }}} 422 407 423 Now Trac drops the connection after serving a page and the connection count on the database will be kept minimal.408 Now Trac drops the connection after serving a page and the connection count on the database will be kept low. 424 409 425 410 //This is not a recommended approach though. See also the notes at the bottom of the [http://code.google.com/p/modwsgi/wiki/IntegrationWithTrac mod_wsgi's IntegrationWithTrac] wiki page.// … … 429 414 For more troubleshooting tips, see also the [TracModPython#Troubleshooting mod_python troubleshooting] section, as most Apache-related issues are quite similar, plus discussion of potential [http://code.google.com/p/modwsgi/wiki/ApplicationIssues application issues] when using mod_wsgi. The wsgi page also has a [http://code.google.com/p/modwsgi/wiki/IntegrationWithTrac Integration With Trac] document. 430 415 431 432 416 ---- 433 See also: 417 See also: TracGuide, TracInstall, [wiki:TracFastCgi FastCGI], [wiki:TracModPython ModPython], [trac:TracNginxRecipe TracNginxRecipe]
