Changes between Version 2 and Version 3 of TracFastCgi

2006-10-08T09:36:47+02:00 (9 years ago)



  • TracFastCgi

    v2 v3  
    2222LoadModule fastcgi_module /usr/lib/apache2/modules/
    24 Setting `FastCgiIpcDir` is optional if the default is suitable.
     24Setting `FastCgiIpcDir` is optional if the default is suitable. Note that the `LoadModule` line must be after the `IfModule` group.
    2626Configure `ScriptAlias` or similar options as described in TracCgi, but
    173173# /trac/chrome/common, and use FastCGI for those
    174174$HTTP["url"] =~ "^/trac(?!/chrome/common)" {
    175 # If you have previous fastcgi.server declarations for applications other than Trac, use += here
    176 # instead of = so you won't overwrite them
     175# Even if you have other fastcgi.server declarations for applications other than Trac, do NOT use += here
    177176fastcgi.server = ("/trac" =>
    178177                   ("trac" =>
    244243  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.
     246== Simple LiteSpeed Configuration ==
     248The FastCGI front-end was developed primarily for use with alternative webservers, such as [ LiteSpeed].
     250LiteSpeed 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.
     2541) Please make sure you have first have a working install of a Trac project. Test install with “tracd” first.
     2562) 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:
     2623) Go “TracVhost → External Apps” tab and create a new “External Application”.
     265Name: MyTracFCGI       
     266Address: uds://tmp/lshttpd/mytracfcgi.sock
     267Max Connections: 10
     268Environment: TRAC_ENV=/fullpathto/mytracproject/ <--- path to root folder of trac project
     269Initial Request Timeout (secs): 30
     270Retry Timeout (secs): 0
     271Persistent Connection   Yes
     272Connection Keepalive Timeout: 30
     273Response Bufferring: No
     274Auto Start: Yes
     275Command: /usr/share/trac/cgi-bin/trac.fcgi  <--- path to trac.fcgi
     276Back Log: 50
     277Instances: 10
     2804) Optional. If you need to use htpasswd based authentication. Go to “TracVhost → Security” tab and create a new security “Realm”.
     283DB Type: Password File
     284Realm Name: MyTracUserDB               <--- any name you wish and referenced later
     285User DB Location: /fullpathto/htpasswd <--- path to your htpasswd file
     288If you don’t have a htpasswd file or don’t know how to create the entries within one, go to, to generate the user:password combos.
     2905) Go to “PythonVhost → Contexts” and create a new “FCGI Context”.
     293URI: /trac/                              <--- URI path to bind to python fcgi app we created   
     294Fast CGI App: [VHost Level] MyTractFCGI  <--- select the trac fcgi extapp we just created
     295Realm: TracUserDB                        <--- only if (4) is set. select ream created in (4)
     2986) Modify /fullpathto/mytracproject/conf/trac.ini
     301#find/set base_rul, url, and link variables
     302base_url = <--- base url to generate correct links to
     303url =      <--- link of project
     304link =     <--- link of graphic logo
     3077) Restart LiteSpeed, “lswsctrl restart”, and access your new Trac project at:
    247314See also TracCgi, TracModPython, TracInstall, TracGuide