Since version 0.9, Trac supports being run through the FastCGI interface. Like mod_python, this allows Trac to remain resident, and is faster than external CGI interfaces which must start a new process for each request. However, unlike mod_python, it is able to support SuEXEC. Additionally, it is supported by much wider variety of web servers.
There are two FastCGI modules commonly available for Apache: mod_fastcgi and mod_fcgid. The FastCgiIpcDir and FastCgiConfig directives discussed below are mod_fastcgiDefaultInitEnv is a mod_fgcid directive. directives; the
For mod_fastcgi, add the following to an appropriate Apache configuration file:
# Enable fastcgi for .fcgi files
Setting FastCgiIpcDir is optional if the default is suitable. Note that the LoadModule line must be after the IfModule group.
Configure ScriptAlias or similar options as described in TracCgi, but calling trac.fcgi instead of trac.cgi.
You can set up the TRAC_ENV as an overall default:
FastCgiConfig -initial-env TRAC_ENV=/path/to/env/trac
Or you can serve multiple Trac projects in a directory like:
FastCgiConfig -initial-env TRAC_ENV_PARENT_DIR=/parent/dir/of/projects
But neither of these will work for mod_fcgid. A similar but partial solution for mod_fcgid is:
DefaultInitEnv TRAC_ENV /path/to/env/trac/
But this cannot be used in Directory or Location context, which makes it difficult to support multiple projects.
A better method which works for both of these modules (and for lighttpd and CGI as well), because it involves no server configuration settings for environment variables, is to set one of the variables in trac.fcgi, e.g.:
Using this method, different projects can be supported by using different .fcgi scripts with different ScriptAliases, copying and appropriately renaming trac.fcgi and adding the above code to create each such script.
The FastCGI front-end was developed primarily for use with alternative webservers, such as lighttpd.
lighttpd is a secure, fast, compliant and very flexible web-server that has been optimized for high-performance environments. It has a very low memory footprint compared to other web servers and takes care of CPU load.
For using trac.fcgi with lighttpd add the following to your lighttpd.conf:
fastcgi.server = ("/trac" =>
Note that you will need to add a new entry to fastcgi.server for each separate Trac instance that you wish to run. Alternatively, you may use the TRAC_ENV_PARENT_DIRTRAC_ENV as described above, and you may set one of the two in trac.fcgi instead of in lighttpd.conf using bin-environment (as in the section above on Apache configuration). variable instead of
For using two projects with lighttpd add the following to your lighttpd.conf:
fastcgi.server = ("/first" =>
Note that field values are different. If you prefer setting the environment variables in the .fcgi scripts, then copy/rename trac.fcgi, e.g., to first.fcgi and second.fcgi, and reference them in the above settings. Note that the above will result in different processes in any event, even if both are running from the same trac.fcgi script.
For authentication you should enable mod_auth in lighttpd.conf 'server.modules', select auth.backend and auth rules:
server.modules = (
Note that lighttpd (I use version 1.4.3) stopped if password file doesn't exist.
Note that lighttpd doesn't support 'valid-user' in versions prior to 1.3.16.
Conditional configuration is also useful for mapping static resources, i.e. serving out images and CSS directly instead of through FastCGI:
# Aliasing functionality is needed
The technique can be easily adapted for use with multiple projects by creating aliases for each of them, and wrapping the fastcgi.server declarations inside conditional configuration blocks. Also there is another way to handle multiple projects and it's to use TRAC_ENV_PARENT_DIR instead of TRAC_ENV and use global auth, let's see an example:
# This is for handling multiple projects
Changing date/time format also supported by lighttpd over environment variable LC_TIME
fastcgi.server = ("/trac" =>
For details about languages specification see TracFaq? question 2.13.
If you use trac-0.9, read about small bug
Relaunch lighttpd, and browse to http://yourhost.example.org/trac to access Trac.
Note about running lighttpd with reduced permissions:
Simple LiteSpeed? Configuration
The FastCGI front-end was developed primarily for use with alternative webservers, such as LiteSpeed.
LiteSpeed? web server is an event-driven asynchronous Apache replacement designed from the ground-up to be secure, scalable, and operate with minimal resources. LiteSpeed? can operate directly from an Apache config file and is targeted for business-critical environments.
1) Please make sure you have first have a working install of a Trac project. Test install with “tracd” first.
2) Create a Virtual Host for this setup. From now on we will refer to this vhost as TracVhost?. For this tutorial we will be assuming that your trac project will be accessible via:
3) Go “TracVhost? → External Apps” tab and create a new “External Application”.
4) Optional. If you need to use htpasswd based authentication. Go to “TracVhost? → Security” tab and create a new security “Realm”.
DB Type: Password File
If you don’t have a htpasswd file or don’t know how to create the entries within one, go to http://sherylcanter.com/encrypt.php, to generate the user:password combos.
5) Go to “PythonVhost? → Contexts” and create a new “FCGI Context”.
URI: /trac/ <--- URI path to bind to python fcgi app we created
6) Modify /fullpathto/mytracproject/conf/trac.ini
#find/set base_rul, url, and link variables
7) Restart LiteSpeed?, “lswsctrl restart”, and access your new Trac project at: