Changes between Version 28 and Version 29 of TracFastCgi

Timestamp:

May 5, 2006, 6:58:56 AM (18 years ago)

Author:

jaboydjr@…

Comment:

Added detail about Apache modules, and optional method for setting env vars in trac.fcgi

TracFastCgi

@@ -4 +4 @@
 
 == Simple Apache configuration ==
+
+There are two FastCGI modules commonly available for Apache: `mod_fastcgi` and
+`mod_fcgid`.  The `FastCgiIpcDir` and `FastCgiConfig` directives discussed
+below are `mod_fastcgi` directives; the `DefaultInitEnv` is a `mod_fgcid`
+directive.
+
+For `mod_fastcgi`, add the following to an appropriate Apache configuration
+file:
 {{{
 # Enable fastcgi for .fcgi files
@@ -14 +22 @@
 LoadModule fastcgi_module /usr/lib/apache2/modules/mod_fastcgi.so
 }}}
-
-You can either setup the `TRAC_ENV` as an overall default:
+Setting `FastCgiIpcDir` is optional if the default is suitable.
+
+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
@@ -25 +37 @@
 }}}
 
-Configure `ScriptAlias` or similar options as described in TracCgi, but calling `trac.fcgi` instead of `trac.cgi`.
-
-In Kubuntu, with libapache2_fcgid (version 1.07), the above did not work, with the error
-{{{
-Invalid command 'FastCgiConfig', perhaps mis-spelled or 
-defined by a module not included in the server configuration.
-}}} 
-when apache is started. The solution was to use 
+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 these variables in `trac.fcgi`, e.g.:
+{{{
+import os
+os.environ['TRAC_ENV'] = "/path/to/projectenv"
+}}}
+or
+{{{
+import os
+os.environ['TRAC_ENV_PARENT_DIR'] = "/path/to/project/parent/dir"
+}}}
+
+Using this method, different projects can be supported by using different
+`.cgi` scripts with different `ScriptAliases`, copying and appropriately
+renaming `trac.fcgi` and adding the above code to create each such script.
 
 == Simple Lighttpd Configuration ==
@@ -58 +83 @@
 }}}
 
-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_DIR` variable instead of `TRAC_ENV` as described  above.
-
-For using two projects with lighttpd add the following to your lighttpd.conf:
+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_DIR` variable instead of `TRAC_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).
+
+For using two projects with lighttpd add the following to your `lighttpd.conf`:
 {{{
 fastcgi.server = ("/first" =>
@@ -82 +109 @@
                 )
 }}}
-Note that field values are different.
+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.
 {{{
 #!html