Changes between Version 2 and Version 3 of TracModWSGI


Ignore:
Timestamp:
Sep 24, 2024, 10:52:05 AM (2 months ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • TracModWSGI

    v2 v3  
    1 = Trac and mod_wsgi =
    2 
    3 
    4 [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 performances.
     1= Trac and mod_wsgi
     2
     3[https://github.com/GrahamDumpleton/mod_wsgi 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.
    54
    65[[PageOutline(2-3,Overview,inline)]]
    … …  
    87== The `trac.wsgi` script
    98
    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).
     9Trac can be run on top of mod_wsgi with the help of an application script, which is a Python file saved with a `.wsgi` extension.
     10
     11A 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. The script should be sufficient for most installations and users not wanting more information can proceed to [#Mappingrequeststothescript configuring Apache].
     12
     13If you are using Trac with multiple projects, you can specify their common parent directory in `trac.wsgi`:
     14{{{#!python
     15def application(environ, start_request):
     16    # Add this when you have multiple projects
     17    environ.setdefault('trac.env_parent_dir', '/usr/share/trac/projects')
     18    ..
     19}}}
     20
     21Directories residing in `trac.env_parent_dir` 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 `trac.env_parent_dir`. Unix [https://docs.python.org/2/library/fnmatch.html shell-style wildcard patterns] can be used in the newline separated list of directories.
    1122
    1223=== A very basic script
     24
    1325In its simplest form, the script could be:
    1426
    … …  
    2335}}}
    2436
    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.
     37The `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`.
     38
     39On Windows:
     40 - If run under the user's session, the Python Egg cache can be found in `%AppData%\Roaming`, for example:
     41{{{#!python
     42os.environ['PYTHON_EGG_CACHE'] = r'C:\Users\Administrator\AppData\Roaming\Python-Eggs'
     43}}}
     44 - If run under a Window service, you should create a directory for Python Egg cache:
     45{{{#!python
     46os.environ['PYTHON_EGG_CACHE'] = r'C:\Trac-Python-Eggs'
     47}}}
    2648
    2749=== A more elaborate script
    2850
    29 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.
     51If 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.
    3052
    3153To solve this problem, use the following `.wsgi` file instead:
    … …  
    3759import trac.web.main
    3860def application(environ, start_response):
    39   environ['trac.env_path'] = '/usr/local/trac/mysite' 
     61  environ['trac.env_path'] = '/usr/local/trac/mysite'
    4062  return trac.web.main.dispatch_request(environ, start_response)
    4163}}}
    4264
    43 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. 
    44 
    45 If you have installed Trac and 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:
     65For 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.
     66
     67If 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:
    4668
    4769{{{#!python
    … …  
    5274Change it according to the path you installed the Trac libs at.
    5375
    54 === Recommended `trac.wsgi` script
    55 
    56 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).
    57 
    58 
    5976== Mapping requests to the script
    6077
    61 After you've done preparing your .wsgi script, add the following to your Apache configuration file (`httpd.conf` for example).
    62 
    63 {{{
     78After preparing your .wsgi script, add the following to your Apache configuration file, typically `httpd.conf`:
     79
     80{{{#!apache
    6481WSGIScriptAlias /trac /usr/local/trac/mysite/apache/mysite.wsgi
    6582
    6683<Directory /usr/local/trac/mysite/apache>
    6784    WSGIApplicationGroup %{GLOBAL}
    68     Order deny,allow
    69     Allow from all
     85    # For Apache 2.2
     86    <IfModule !mod_authz_core.c>
     87        Order deny,allow
     88        Allow from all
     89    </IfModule>
     90    # For Apache 2.4
     91    <IfModule mod_authz_core.c>
     92        Require all granted
     93    </IfModule>
    7094</Directory>
    7195}}}
    … …  
    7397Here, the script is in a subdirectory of the Trac environment.
    7498
    75 If you followed the directions [http://trac.edgewall.org/wiki/TracInstall#cgi-bin Generating the Trac cgi-bin directory], your Apache configuration file should look like following:
    76 
    77 {{{
     99If you followed the directions [TracInstall#cgi-bin Generating the Trac cgi-bin directory], your Apache configuration file should look like following:
     100
     101{{{#!apache
    78102WSGIScriptAlias /trac /usr/share/trac/cgi-bin/trac.wsgi
    79103
    80104<Directory /usr/share/trac/cgi-bin>
    81105    WSGIApplicationGroup %{GLOBAL}
    82     Order deny,allow
    83     Allow from all
     106    # For Apache 2.2
     107    <IfModule !mod_authz_core.c>
     108        Order deny,allow
     109        Allow from all
     110    </IfModule>
     111    # For Apache 2.4
     112    <IfModule mod_authz_core.c>
     113        Require all granted
     114    </IfModule>
    84115</Directory>
    85116}}}
    86117
    87 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.
    88 
    89 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):
     118In 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.
     119
     120To 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):
    90121
    91122{{{#!python
    … …  
    95126}}}
    96127
    97 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.
    98 
     128For more information about using the mod_wsgi specific directives, see the [https://code.google.com/archive/p/modwsgi/wikis mod_wsgi's wiki] and more specifically the [https://code.google.com/archive/p/modwsgi/wikis/IntegrationWithTrac.wiki IntegrationWithTrac] page.
    99129
    100130== Configuring Authentication
    101131
    102 We describe in the the following sections different methods for setting up authentication.
    103 
    104 See also [http://httpd.apache.org/docs/2.2/howto/auth.html Authentication, Authorization and Access Control] in the Apache guide.
    105 
    106 === Using Basic Authentication ===
    107 
    108 The simplest way to enable authentication with Apache is to create a password file. Use the `htpasswd` program to create the password file:
    109 {{{
     132The following sections describe different methods for setting up authentication. See also [https://httpd.apache.org/docs/2.4/howto/auth.html Authentication, Authorization and Access Control] in the Apache guide.
     133
     134=== Using Basic Authentication
     135
     136The simplest way to enable authentication with Apache is to create a password file. Use the `htpasswd` program as follows:
     137{{{#!sh
    110138$ htpasswd -c /somewhere/trac.htpasswd admin
    111139New password: <type password>
    … …  
    114142}}}
    115143
    116 After the first user, you dont need the "-c" option anymore:
    117 {{{
     144After the first user, you don't need the "-c" option anymore:
     145{{{#!sh
    118146$ htpasswd /somewhere/trac.htpasswd john
    119147New password: <type password>
    … …  
    122150}}}
    123151
    124   ''See the man page for `htpasswd` for full documentation.''
     152See the man page for `htpasswd` for full documentation.
    125153
    126154After you've created the users, you can set their permissions using TracPermissions.
    127155
    128 Now, you'll need to enable authentication against the password file in the Apache configuration:
    129 {{{
     156Now, you need to enable authentication against the password file in the Apache configuration:
     157{{{#!apache
    130158<Location "/trac/login">
    131159  AuthType Basic
    … …  
    136164}}}
    137165
    138 If you're hosting multiple projects you can use the same password file for all of them:
    139 {{{
     166If you are hosting multiple projects, you can use the same password file for all of them:
     167{{{#!apache
    140168<LocationMatch "/trac/[^/]+/login">
    141169  AuthType Basic
    … …  
    145173</LocationMatch>
    146174}}}
    147 Note that neither a file nor a directory named 'login' needs to exist.[[BR]]
    148 See also the [http://httpd.apache.org/docs/2.2/mod/mod_auth_basic.html mod_auth_basic] documentation.
    149 
    150 === Using Digest Authentication ===
    151 
    152 For better security, it is recommended that you either enable SSL or at least use the “digest” authentication scheme instead of “Basic”.
    153 
    154 You'll have to create your `.htpasswd` file with the `htdigest` command instead of `htpasswd`, as follows:
    155 {{{
    156 # htdigest -c /somewhere/trac.htpasswd trac admin
     175
     176Note that neither a file nor a directory named 'login' needs to exist. See also the [https://httpd.apache.org/docs/2.4/mod/mod_auth_basic.html mod_auth_basic] documentation.
     177
     178=== Using Digest Authentication
     179
     180For better security, it is recommended that you either enable SSL or at least use the "digest" authentication scheme instead of "Basic".
     181
     182You have to create your `.htpasswd` file with the `htdigest` command instead of `htpasswd`, as follows:
     183{{{#!sh
     184$ htdigest -c /somewhere/trac.htpasswd trac admin
    157185}}}
    158186
    159187The "trac" parameter above is the "realm", and will have to be reused in the Apache configuration in the !AuthName directive:
    160188
    161 {{{
     189{{{#!apache
    162190<Location "/trac/login">
    163 
    164     AuthType Digest
    165     AuthName "trac"
    166     AuthDigestDomain /trac
    167     AuthUserFile /somewhere/trac.htpasswd
    168     Require valid-user
     191  AuthType Digest
     192  AuthName "trac"
     193  AuthDigestDomain /trac
     194  AuthUserFile /somewhere/trac.htpasswd
     195  Require valid-user
    169196</Location>
    170197}}}
    … …  
    172199For multiple environments, you can use the same `LocationMatch` as described with the previous method.
    173200
     201'''Note''': `Location` cannot be used inside .htaccess files, but must instead live within the main httpd.conf file. If you are on a shared server, you therefore will not be able to provide this level of granularity.
     202
    174203Don't forget to activate the mod_auth_digest. For example, on a Debian 4.0r1 (etch) system:
    175 {{{
    176     LoadModule auth_digest_module /usr/lib/apache2/modules/mod_auth_digest.so
    177 }}}
    178 
    179 
    180 See also the [http://httpd.apache.org/docs/2.2/mod/mod_auth_digest.html mod_auth_digest] documentation.
    181 
    182 === Using LDAP Authentication
    183 
    184 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)
    185 
    186 1. You need to load the following modules in Apache httpd.conf
    187 {{{
    188 LoadModule ldap_module modules/mod_ldap.so
    189 LoadModule authnz_ldap_module modules/mod_authnz_ldap.so
    190 }}}
    191 
    192 2. Your httpd.conf also needs to look something like:
    193 
    194 {{{
     204{{{#!apache
     205  LoadModule auth_digest_module /usr/lib/apache2/modules/mod_auth_digest.so
     206}}}
     207
     208See also the [https://httpd.apache.org/docs/2.4/mod/mod_auth_basic.html mod_auth_digest] documentation.
     209
     210=== Using LDAP Authentication
     211
     212Configuration for [https://httpd.apache.org/docs/2.4/mod/mod_ldap.html mod_ldap] authentication in Apache is more involved (httpd 2.2+ and OpenLDAP: slapd 2.3.19).
     213
     2141. You need to load the following modules in Apache httpd.conf:
     215{{{#!apache
     216  LoadModule ldap_module modules/mod_ldap.so
     217  LoadModule authnz_ldap_module modules/mod_authnz_ldap.so
     218}}}
     2191. Your httpd.conf also needs to look something like:
     220{{{#!apache
    195221<Location /trac/>
    196222  # (if you're using it, mod_python specific settings go here)
    … …  
    206232</Location>
    207233}}}
    208 
    209 
    210 3. You can use the LDAP interface as a way to authenticate to a Microsoft Active Directory:
    211 
    212 
    213 Use the following as your LDAP URL:
    214 {{{
    215     AuthLDAPURL "ldap://directory.example.com:3268/DC=example,DC=com?sAMAccountName?sub?(objectClass=user)"
    216 }}}
    217 
    218 You will also need to provide an account for Apache to use when checking
    219 credentials. As this password will be listed in plaintext in the
    220 config, you should be sure to use an account specifically for this task:
    221 {{{
    222     AuthLDAPBindDN ldap-auth-user@example.com
    223     AuthLDAPBindPassword "password"
    224 }}}
    225 
    226 The whole section looks like:
    227 {{{
     2341. You can use the LDAP interface as a way to authenticate to a Microsoft Active Directory. Use the following as your LDAP URL:
     235{{{#!apache
     236  AuthLDAPURL "ldap://directory.example.com:3268/DC=example,DC=com?sAMAccountName?sub?(objectClass=user)"
     237}}}
     238 You will also need to provide an account for Apache to use when checking credentials. As this password will be listed in plain text in the configuration, you need to use an account specifically for this task:
     239{{{#!apache
     240  AuthLDAPBindDN ldap-auth-user@example.com
     241  AuthLDAPBindPassword "password"
     242}}}
     243 The whole section looks like:
     244{{{#!apache
    228245<Location /trac/>
    229246  # (if you're using it, mod_python specific settings go here)
    … …  
    239256  authzldapauthoritative Off
    240257  # require valid-user
    241   require ldap-group CN=Trac Users,CN=Users,DC=company,DC=com
     258  Require ldap-group CN=Trac Users,CN=Users,DC=company,DC=com
    242259</Location>
    243260}}}
    244261
    245 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.
    246 
    247 Note 2: You can also require the user be a member of a certain LDAP group, instead of
    248 just having a valid login:
    249 {{{
    250     Require ldap-group CN=Trac Users,CN=Users,DC=example,DC=com
     262Note 1: This is the case where the LDAP search will get around the multiple OUs, connecting 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.
     263
     264Note 2: You can also require the user be a member of a certain LDAP group, instead of just having a valid login:
     265{{{#!apache
     266  Require ldap-group CN=Trac Users,CN=Users,DC=example,DC=com
    251267}}}
    252268
    253269See also:
    254   - [http://httpd.apache.org/docs/2.2/mod/mod_authnz_ldap.html mod_authnz_ldap], documentation for mod_authnz_ldap
    255    
    256  - [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.
    257  - [http://trac-hacks.org/wiki/LdapPlugin TracHacks:LdapPlugin] for storing TracPermissions in LDAP.
     270 - [https://httpd.apache.org/docs/2.4/mod/mod_authnz_ldap.html mod_authnz_ldap], documentation for mod_authnz_ldap.
     271 - [https://httpd.apache.org/docs/2.4/mod/mod_ldap.html mod_ldap], documentation for mod_ldap, which provides connection pooling and a shared cache.
     272 - [https://trac-hacks.org/wiki/LdapPlugin TracHacks:LdapPlugin] for storing TracPermissions in LDAP.
    258273
    259274=== Using SSPI Authentication
    260275
    261 If you are using Apache on Windows, you can use mod_auth_sspi to provide
    262 single-sign-on. Download the module from the !SourceForge [http://sourceforge.net/projects/mod-auth-sspi/ mod-auth-sspi project] and then add the
    263 following to your !VirtualHost:
    264 {{{
    265     <Location /trac/login>
    266         AuthType SSPI
    267         AuthName "Trac Login"
    268         SSPIAuth On
    269         SSPIAuthoritative On
    270         SSPIDomain MyLocalDomain
    271         SSPIOfferBasic On
    272         SSPIOmitDomain Off
    273         SSPIBasicPreferred On
    274         Require valid-user
    275     </Location>
    276 }}}
    277 
    278 Using the above, usernames in Trac will be of the form `DOMAIN\username`, so
    279 you may have to re-add permissions and such. If you do not want the domain to
    280 be part of the username, set `SSPIOmitDomain On` instead.
     276If you are using Apache on Windows, you can use mod_auth_sspi to provide single-sign-on. Download the module from the !SourceForge [https://sourceforge.net/projects/mod-auth-sspi/ mod-auth-sspi project] and then add the following to your !VirtualHost:
     277{{{#!apache
     278<Location /trac/login>
     279  AuthType SSPI
     280  AuthName "Trac Login"
     281  SSPIAuth On
     282  SSPIAuthoritative On
     283  SSPIDomain MyLocalDomain
     284  SSPIOfferBasic On
     285  SSPIOmitDomain Off
     286  SSPIBasicPreferred On
     287  Require valid-user
     288</Location>
     289}}}
     290
     291Using 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.
    281292
    282293Some common problems with SSPI authentication: [trac:#1055], [trac:#1168] and [trac:#3338].
    … …  
    284295See also [trac:TracOnWindows/Advanced].
    285296
    286 === Using Apache authentication with the Account Manager plugin's Login form ===
    287 
    288 To begin with, see the basic instructions for using the Account Manager plugin's [http://trac-hacks.org/wiki/AccountManagerPlugin/Modules#LoginModule Login module] and its [http://trac-hacks.org/wiki/AccountManagerPlugin/AuthStores#HttpAuthStore HttpAuthStore authentication module].
    289 
    290 '''Note:''' If is difficult to get !HttpAuthStore to work with WSGI when using any Account Manager version prior to acct_mgr-0.4. Upgrading is recommended.
    291 
    292 Here is an example (from the !HttpAuthStore link) using acct_mgr-0.4 for hosting a single project:
    293 {{{
    294 [components]
    295 ; be sure to enable the component
    296 acct_mgr.http.HttpAuthStore = enabled
    297 
    298 [account-manager]
    299 ; configure the plugin to use a page that is secured with http authentication
    300 authentication_url = /authFile
    301 password_store = HttpAuthStore
    302 }}}
    303 This will generally be matched with an Apache config like:
    304 {{{
    305 <Location /authFile>
    306    …HTTP authentication configuration…
    307    Require valid-user
    308 </Location>
    309 }}}
    310 Note that '''authFile''' need not exist. See the !HttpAuthStore link above for examples where multiple Trac projects are hosted on a server.
     297=== Using CA !SiteMinder Authentication
     298
     299Setup CA !SiteMinder to protect your Trac login URL, for example `/trac/login`. Also, make sure the policy is set to include the HTTP_REMOTE_USER variable. If your site allows it, you can set this in `LocalConfig.conf`:
     300{{{#!apache
     301RemoteUserVar="WHATEVER_IT_SHOULD_BE"
     302SetRemoteUser="YES"
     303}}}
     304
     305The specific variable is site-dependent. Ask your site administrator. If your site does not allow the use of `LocalConfig.conf` for security reasons, have your site administrator set the policy on the server to set REMOTE_USER.
     306
     307Also add a !LogOffUri parameter to the agent configuration, for example `/trac/logout`.
     308
     309Then modify the trac.wsgi script generated using `trac-admin <env> deploy <dir>` to add the following lines, which extract the `HTTP_REMOTE_USER` variable and set it to `REMOTE_USER`:
     310
     311{{{#!python
     312def application(environ, start_request):
     313    # Set authenticated username on CA SiteMinder to REMOTE_USER variable
     314    # strip() is used to remove any spaces on the end of the string
     315    if 'HTTP_SM_USER' in environ:
     316        environ['REMOTE_USER'] = environ['HTTP_REMOTE_USER'].strip()
     317    ...
     318}}}
     319
     320You do not need any Apache "Location" directives.
    311321
    312322=== Example: Apache/mod_wsgi with Basic Authentication, Trac being at the root of a virtual host
    313323
    314 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.
    315 
    316 
    317 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:
     324Per the mod_wsgi documentation linked to above, here is an example Apache configuration that:
     325 - serves the Trac instance from a virtualhost subdomain
     326 - uses Apache basic authentication for Trac authentication.
     327
     328If you want your Trac to be served from eg !http://trac.my-proj.my-site.org, then from the folder eg `/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:
    318329
    319330Create the htpasswd file:
    320 {{{
     331{{{#!sh
    321332cd /home/trac-for-my-proj/the-env
    322333htpasswd -c htpasswd firstuser
    … …  
    324335htpasswd htpasswd seconduser
    325336}}}
    326 (keep the file above your document root for security reasons)
    327 
    328 Create this file e.g. (ubuntu) `/etc/apache2/sites-enabled/trac.my-proj.my-site.org.conf` with the following contents:
    329 
    330 {{{
     337
     338Keep the file above your document root for security reasons.
     339
     340Create this file for example `/etc/apache2/sites-enabled/trac.my-proj.my-site.org.conf` on Ubuntu with the following content:
     341
     342{{{#!apache
    331343<Directory /home/trac-for-my-proj/the-deploy/cgi-bin/trac.wsgi>
    332344  WSGIApplicationGroup %{GLOBAL}
    … …  
    349361}}}
    350362
    351 Note: for subdomains to work you would probably also need to alter `/etc/hosts` and add A-Records to your host's DNS.
    352 
     363For subdomains to work you would probably also need to alter `/etc/hosts` and add A-Records to your host's DNS.
    353364
    354365== Troubleshooting
    … …  
    356367=== Use a recent version
    357368
    358 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].
    359 
    360 ''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''
    361 
    362 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).
    363 
    364 === Getting Trac to work nicely with SSPI and 'Require Group' ===
    365 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'.
    366 
    367 This WSGI script 'fixes' things, hope it helps:
     369Please 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 [https://code.google.com/archive/p/modwsgi/issues/100 #100] and [https://code.google.com/archive/p/modwsgi/issues/132 #132].
     370
     371'''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 [https://www.mail-archive.com/modwsgi@googlegroups.com/msg01917.html here]) solved this for me[[BR]]-- Graham Shanks
     372
     373If you plan to use `mod_wsgi` in embedded mode on Windows or with the MPM worker on Linux, then you will need version 3.4 or greater. See [trac:#10675] for details.
     374
     375=== Getting Trac to work nicely with SSPI and 'Require Group'
     376
     377If 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'.
     378
     379This WSGI script fixes that:
    368380{{{#!python
    369381import os
    … …  
    379391}}}
    380392
    381 
    382 === Trac with PostgreSQL ===
    383 
    384 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.
    385 
    386 A somewhat brutal workaround is to disabled connection pooling in Trac. This is done by setting `poolable = False` in `trac.db.postgres_backend` on the `PostgreSQLConnection` class.
    387 
    388 But it's not necessary to edit the source of Trac, the following lines in `trac.wsgi` will also work:
    389 
    390 {{{
     393=== Trac with PostgreSQL
     394
     395When 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.
     396
     397A 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.
     398
     399But it is not necessary to edit the source of Trac. The following lines in `trac.wsgi` will also work:
     400
     401{{{#!python
    391402import trac.db.postgres_backend
    392403trac.db.postgres_backend.PostgreSQLConnection.poolable = False
    … …  
    395406or
    396407
    397 {{{
     408{{{#!python
    398409import trac.db.mysql_backend
    399410trac.db.mysql_backend.MySQLConnection.poolable = False
    400411}}}
    401412
    402 Now Trac drops the connection after serving a page and the connection count on the database will be kept minimal.
    403 
    404 //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.//
     413Now Trac drops the connection after serving a page and the connection count on the database will be kept low.
     414
     415//This is not a recommended approach though. See also the notes at the bottom of the [https://code.google.com/archive/p/modwsgi/wikis/IntegrationWithTrac.wiki mod_wsgi's IntegrationWithTrac] wiki page.//
    405416
    406417=== Other resources
    407418
    408 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.
    409 
     419For more troubleshooting tips, see also the [TracModPython#Troubleshooting mod_python troubleshooting] section, as most Apache-related issues are quite similar, plus discussion of potential [https://code.google.com/archive/p/modwsgi/wikis/ApplicationIssues.wiki application issues] when using mod_wsgi. The wsgi page also has a [https://code.google.com/archive/p/modwsgi/wikis/IntegrationWithTrac.wiki Integration With Trac] document.
    410420
    411421----
    412 See also:  TracGuide, TracInstall, [wiki:TracFastCgi FastCGI], [wiki:TracModPython ModPython], [trac:TracNginxRecipe TracNginxRecipe]
     422See also: TracGuide, TracInstall, [wiki:TracFastCgi FastCGI], [wiki:TracModPython ModPython], [trac:TracNginxRecipe TracNginxRecipe]