Edgewall Software

Changes between Version 60 and Version 61 of TracFastCgi


Ignore:
Timestamp:
Apr 6, 2010, 8:31:04 PM (14 years ago)
Author:
Christian Boos
Comment:

a few random clean-ups

Legend:

Unmodified
Added
Removed
Modified

  • TracFastCgi

    v60 v61  
    123123using `bin-environment` (as in the section above on Apache configuration).
    124124
    125 Note that lighttpd have a bug related to 'SCRIPT_NAME' and 'PATH_INFO' when the uri of fastcgi.server is '/' instead of '/trac' in this example, see #2418. This should be fixed since lighttpd 1.4.23, and you may need to add "fix-root-scriptname" => "enable" as parameter of fastcgi.server.
     125Note that lighttpd have 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.
    126126
    127127For using two projects with lighttpd add the following to your `lighttpd.conf`:
    … …  
    277277Note about running lighttpd with reduced permissions:
    278278
    279   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.
     279  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.
    280280
    281281
    … …  
    286286!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.
    287287
    288 Setup
    289 
    290 1) Please make sure you have first have a working install of a Trac project. Test install with “tracd” first.
    291 
    292 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:
     288=== Setup ===
     289
     290 1. Please make sure you have first have a working install of a Trac project. Test install with “tracd” first.
     291
     292 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:
    293293
    294294{{{
    … …  
    296296}}}
    297297
    298 3) Go “TracVhost → External Apps” tab and create a new “External Application”.
     298 3. Go “!TracVhost → External Apps” tab and create a new “External Application”.
    299299
    300300{{{
    … …  
    314314}}}
    315315
    316 4) Optional. If you need to use htpasswd based authentication. Go to “TracVhost → Security” tab and create a new security “Realm”.
     316 4. Optional. If you need to use htpasswd based authentication. Go to “!TracVhost → Security” tab and create a new security “Realm”.
    317317
    318318{{{
    … …  
    324324If 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.
    325325
    326 5) Go to “PythonVhost → Contexts” and create a new “FCGI Context”.
     326 5. Go to “!PythonVhost → Contexts” and create a new “FCGI Context”.
    327327
    328328{{{
    … …  
    332332}}}
    333333
    334 6) Modify /fullpathto/mytracproject/conf/trac.ini
     334 6. Modify `/fullpathto/mytracproject/conf/trac.ini`
    335335
    336336{{{
    … …  
    341341}}}
    342342
    343 7) Restart !LiteSpeed, “lswsctrl restart”, and access your new Trac project at:
     343 7. Restart !LiteSpeed, “lswsctrl restart”, and access your new Trac project at:
    344344
    345345{{{
    … …  
    347347}}}
    348348
    349 === Simple Nginx Configuration ===
    350 
    351 1) Nginx configuration snippet - confirmed to work on 0.6.32
     349== Simple Nginx Configuration ==
     350
     351 1. Nginx configuration snippet - confirmed to work on 0.6.32
    352352{{{
    353353    server {
    … …  
    405405}}}
    406406
    407 2) Modified trac.fcgi:
     407 2. Modified trac.fcgi:
    408408
    409409{{{
    … …  
    439439}}}
    440440
    441 3) reload nginx and launch trac.fcgi like that:
     441 3. reload nginx and launch trac.fcgi like that:
    442442
    443443{{{
    … …  
    447447The above assumes that:
    448448 * There is a user named 'trac' for running trac instances and keeping trac environments in its home directory.
    449  * /home/trac/instance contains a trac environment
    450  * /home/trac/htpasswd contains authentication information
    451  * /home/trac/run is owned by the same group the nginx runs under
    452   * and if your system is Linux the /home/trac/run has setgid bit set (chmod g+s run)
     449 * `/home/trac/instance` contains a trac environment
     450 * `/home/trac/htpasswd` contains authentication information
     451 * `/home/trac/run` is owned by the same group the nginx runs under
     452  * and if your system is Linux the `/home/trac/run` has setgid bit set (`chmod g+s run`)
    453453  * and patch from ticket #T7239 is applied, or you'll have to fix the socket file permissions every time
    454454