Trac and mod_wsgi

Important note: Please use either version 1.3 or 2.3 or later of mod_wsgi. Version 2.0 has problems with downloading attachments (see [trac:#7205 #7205]).

mod_wsgi is an Apache module for running WSGI-compatible Python applications directly on top of Apache:

The mod_wsgi adapter is an Apache module that provides a WSGI compliant interface for hosting Python based web applications within Apache. The adapter is written completely in C code against the Apache C runtime and for hosting WSGI applications within Apache provides significantly better performance than using existing WSGI adapters for mod_python or CGI.

It is already possible to run Trac on top of mod_wsgi. This can be done by writing the following application script, which is just a Python file, though usually saved with a .wsgi extension).

import os

os.environ['TRAC_ENV'] = '/usr/local/trac/mysite'
os.environ['PYTHON_EGG_CACHE'] = '/usr/local/trac/mysite/eggs'

import trac.web.main
application = trac.web.main.dispatch_request


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 on top of the wsgi script:
import site
Change it according to the path you installed the trac libs at.

After you've done preparing your wsgi-script, add the following to your httpd.conf.

WSGIScriptAlias /trac /usr/local/trac/mysite/apache/mysite.wsgi

<Directory /usr/local/trac/mysite/apache>
    WSGIApplicationGroup %{GLOBAL}
    Order deny,allow
    Allow from all


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):

def application(environ, start_response):
        start_response('200 OK',[('Content-type','text/html')])
        return ['<html><body>Hello World!</body></html>']

See also the mod_wsgi "installation instructions": for Trac.

For troubleshooting tips, see the [TracModPython#Troubleshooting mod_python troubleshooting] section, as most Apache-related issues are quite similar, plus discussion of potential "application issues": when using mod_wsgi.

h2. Trac with [[PostgreSQL]]

When using the mod_wsgi adapter with multiple Trac instances and [[PostgreSQL]] (or [[MySQL]]?) as a database back-end the server can get a lot of open database connections. (and thus [[PostgreSQL]] processes)

A workable solution is to disabled connection pooling in Trac. This is done by setting poolable = False in trac.db.postgres_backend on the [[PostgreSQLConnection]] class.

But it's not necessary to edit the source of trac, the following lines in trac.wsgi will also work:

import trac.db.postgres_backend
trac.db.postgres_backend.PostgreSQLConnection.poolable = False

Now Trac drops the connection after serving a page and the connection count on the database will be kept minimal.

Updated by about 13 years ago · 2 revisions