Changes between Version 2 and Version 3 of TracFastCgi

Timestamp:

Nov 24, 2010, 2:12:18 PM (15 years ago)

Author:

trac

Comment:

--

TracFastCgi

@@ -45 +45 @@
 
 To setup Trac environment for `mod_fcgid` it is necessary to use
-`FCGIDDefaultInitEnv` directive. It cannot be used in `Directory` or
+`DefaultInitEnv` directive. It cannot be used in `Directory` or
 `Location` context, so if you need to support multiple projects, try
 alternative environment setup below.
 
 {{{
-FCGIDDefaultInitEnv TRAC_ENV /path/to/env/trac/
+DefaultInitEnv TRAC_ENV /path/to/env/trac/
 }}}
 
@@ -122 +122 @@
 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).
+
+Note that lighttpd has a bug related to 'SCRIPT_NAME' and 'PATH_INFO' when the uri of fastcgi.server is '/' instead of '/trac' in this example, see #Trac2418. This should be fixed since lighttpd 1.4.23, and you may need to add `"fix-root-scriptname" => "enable"` as parameter of fastcgi.server.
 
 For using two projects with lighttpd add the following to your `lighttpd.conf`:
@@ -275 +277 @@
 Note about running lighttpd with reduced permissions:
 
-  If nothing else helps and trac.fcgi doesn't start with lighttpd settings __server.username = "www-data"__, __server.groupname = "www-data"__, then in the `bin-environment` section set `PYTHON_EGG_CACHE` to the home directory of `www-data` or some other directory accessible to this account for writing.
+  If nothing else helps and trac.fcgi doesn't start with lighttpd settings `server.username = "www-data"`, `server.groupname = "www-data"`, then in the `bin-environment` section set `PYTHON_EGG_CACHE` to the home directory of `www-data` or some other directory accessible to this account for writing.
 
 
@@ -284 +286 @@
 !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.
 
-Setup
-
-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:
+=== Setup ===
+
+ 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:
 
 {{{
@@ -294 +296 @@
 }}}
 
-3) Go “TracVhost → External Apps” tab and create a new “External Application”.
+ 3. Go “!TracVhost → External Apps” tab and create a new “External Application”.
 
 {{{
@@ -312 +314 @@
 }}}
 
-4) Optional. If you need to use htpasswd based authentication. Go to “TracVhost → Security” tab and create a new security “Realm”.
+ 4. Optional. If you need to use htpasswd based authentication. Go to “!TracVhost → Security” tab and create a new security “Realm”.
 
 {{{
@@ -322 +324 @@
 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”.
+ 5. Go to “!PythonVhost → Contexts” and create a new “FCGI Context”.
 
 {{{
@@ -330 +332 @@
 }}}
 
-6) Modify /fullpathto/mytracproject/conf/trac.ini
+ 6. Modify `/fullpathto/mytracproject/conf/trac.ini`
 
 {{{
@@ -339 +341 @@
 }}}
 
-7) Restart !LiteSpeed, “lswsctrl restart”, and access your new Trac project at: 
+ 7. Restart !LiteSpeed, “lswsctrl restart”, and access your new Trac project at: 
 
 {{{
@@ -345 +347 @@
 }}}
 
-=== Simple Nginx Configuration ===
-
-1) Nginx configuration snippet - confirmed to work on 0.6.32
+== Simple Nginx Configuration ==
+
+ 1. Nginx configuration snippet - confirmed to work on 0.6.32
 {{{
     server {
@@ -394 +396 @@
             fastcgi_param  SERVER_PORT        $server_port;
             fastcgi_param  SERVER_PROTOCOL    $server_protocol;
+            fastcgi_param  QUERY_STRING     $query_string;
 
             # for authentication to work
@@ -402 +405 @@
 }}}
 
-2) Modified trac.fcgi:
+ 2. Modified trac.fcgi:
 
 {{{
@@ -436 +439 @@
 }}}
 
-3) reload nginx and launch trac.fcgi like that:
+ 3. reload nginx and launch trac.fcgi like that:
 
 {{{
@@ -444 +447 @@
 The above assumes that:
  * There is a user named 'trac' for running trac instances and keeping trac environments in its home directory.
- * /home/trac/instance contains a trac environment
- * /home/trac/htpasswd contains authentication information
- * /home/trac/run is owned by the same group the nginx runs under
-  * and if your system is Linux the /home/trac/run has setgid bit set (chmod g+s run)
+ * `/home/trac/instance` contains a trac environment
+ * `/home/trac/htpasswd` contains authentication information
+ * `/home/trac/run` is owned by the same group the nginx runs under
+  * and if your system is Linux the `/home/trac/run` has setgid bit set (`chmod g+s run`)
   * and patch from ticket #T7239 is applied, or you'll have to fix the socket file permissions every time