Changes between Version 1 and Version 2 of TracFastCgi


Ignore:
Timestamp:
Feb 24, 2010 5:37:18 PM (9 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracFastCgi

    v1 v2  
    11= Trac with FastCGI =
    22
    3 Since version 0.9, Trac supports being run through the [http://www.fastcgi.com/ FastCGI] interface. Like [wiki:TracModPython 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 [http://httpd.apache.org/docs/suexec.html SuEXEC]. Additionally, it is supported by much wider variety of web servers.
    4 
    5 {{{
    6 #!html
    7 <p style="background: #fdc; border: 2px solid #d00; font-style: italic; padding: 0 .5em; margin: 1em 0;">
    8 <strong>Note for Windows:</strong> Trac's FCGI does not run under Windows, as Windows does not implement Socket.fromfd, which is used by _fcgi.py
    9 </p>
    10 }}}
     3[http://www.fastcgi.com/ FastCGI] interface allows Trac to remain resident much like with [wiki:TracModPython mod_python]. It is faster than external CGI interfaces which must start a new process for each request. However, unlike mod_python, FastCGI supports [http://httpd.apache.org/docs/suexec.html Apache SuEXEC], i.e. run with different permissions than web server. Additionally, it is supported by much wider variety of web servers.
     4
     5'''Note for Windows:''' Trac's FastCGI does not run under Windows, as Windows does not implement `Socket.fromfd`, which is used by `_fcgi.py`. If you want to connect to IIS, you may want to try [trac:TracOnWindowsIisAjp AJP].
    116
    127== Simple Apache configuration ==
    138
    149There are two FastCGI modules commonly available for Apache: `mod_fastcgi` and
    15 `mod_fcgid`.  The `FastCgiIpcDir` and `FastCgiConfig` directives discussed
    16 below are `mod_fastcgi` directives; the `DefaultInitEnv` is a `mod_fcgid`
    17 directive.
    18 
    19 For `mod_fastcgi`, add the following to an appropriate Apache configuration
    20 file:
     10`mod_fcgid` (preferred). The latter is more up-to-date.
     11
     12==== setup with `mod_fastcgi` ====
     13`mod_fastcgi` uses `FastCgiIpcDir` and `FastCgiConfig` directives that should be added to an appropriate Apache configuration file:
    2114{{{
    2215# Enable fastcgi for .fcgi files
     
    4437}}}
    4538
    46 But neither of these will work for `mod_fcgid`.  A similar but partial
    47 solution for `mod_fcgid` is:
    48 {{{
    49 DefaultInitEnv TRAC_ENV /path/to/env/trac/
    50 }}}
    51 But this cannot be used in `Directory` or `Location` context, which makes it
    52 difficult to support multiple projects.
    53 
    54 A better method which works for both of these modules (and for  [http://www.lighttpd.net/ lighttpd] and CGI as well), because it involves
    55 no server configuration settings for environment variables, is to set one
    56 of the variables in `trac.fcgi`, e.g.:
     39==== setup with `mod_fcgid` ====
     40Configure `ScriptAlias` (see TracCgi for details), but call `trac.fcgi`
     41instead of `trac.cgi`. Note that slash at the end - it is important.
     42{{{
     43ScriptAlias /trac /path/to/www/trac/cgi-bin/trac.fcgi/
     44}}}
     45
     46To setup Trac environment for `mod_fcgid` it is necessary to use
     47`FCGIDDefaultInitEnv` directive. It cannot be used in `Directory` or
     48`Location` context, so if you need to support multiple projects, try
     49alternative environment setup below.
     50
     51{{{
     52FCGIDDefaultInitEnv TRAC_ENV /path/to/env/trac/
     53}}}
     54
     55==== alternative environment setup ====
     56A better method to specify path to Trac environment it to embed the path
     57into `trac.fcgi` script itself. That doesn't require configuration of server
     58environment variables, works for both FastCgi modules
     59(and for [http://www.lighttpd.net/ lighttpd] and CGI as well):
    5760{{{
    5861import os
     
    6568}}}
    6669
    67 Using this method, different projects can be supported by using different
    68 `.fcgi` scripts with different `ScriptAliases`, copying and appropriately
    69 renaming `trac.fcgi` and adding the above code to create each such script.
     70With this method different projects can be supported by using different
     71`.fcgi` scripts with different `ScriptAliases`.
    7072
    7173See [https://coderanger.net/~coderanger/httpd/fcgi_example.conf this fcgid example config] which uses a !ScriptAlias directive with trac.fcgi with a trailing / like this:
     
    7678== Simple Cherokee Configuration ==
    7779
    78 Configuration wanted.
     80The configuration on Cherokee's side is quite simple. You will only need to know that you can spawn Trac as an SCGI process.
     81You can either start it manually, or better yet, automatically by letting Cherokee spawn the server whenever it is down.
     82First set up an information source in cherokee-admin with a local interpreter.
     83
     84{{{
     85Host:
     86localhost:4433
     87
     88Interpreter:
     89/usr/bin/tracd —single-env —daemonize —protocol=scgi —hostname=localhost —port=4433 /path/to/project/
     90}}}
     91
     92If the port was not reachable, the interpreter command would be launched. Note that, in the definition of the information source, you will have to manually launch the spawner if you use a ''Remote host'' as ''Information source'' instead of a ''Local interpreter''.
     93
     94After doing this, we will just have to create a new rule managed by the SCGI handler to access Trac. It can be created in a new virtual server, trac.example.net for instance, and will only need two rules. The '''default''' one will use the SCGI handler associated to the previously created information source.
     95The second rule will be there to serve the few static files needed to correctly display the Trac interface. Create it as ''Directory rule'' for ''/chrome/common'' and just set it to the ''Static files'' handler and with a ''Document root'' that points to the appropriate files: ''/usr/share/trac/htdocs/''
    7996
    8097== Simple Lighttpd Configuration ==
     
    85102environments.  It has a very low memory footprint compared to other web servers and takes care of CPU load.
    86103
    87 For using `trac.fcgi` with lighttpd add the following to your lighttpd.conf:
    88 {{{
     104For using `trac.fcgi`(prior to 0.11) / fcgi_frontend.py (0.11) with lighttpd add the following to your lighttpd.conf:
     105{{{
     106#var.fcgi_binary="/usr/bin/python /path/to/fcgi_frontend.py" # 0.11 if installed with easy_setup, it is inside the egg directory
     107var.fcgi_binary="/path/to/cgi-bin/trac.fcgi" # 0.10 name of prior fcgi executable
    89108fastcgi.server = ("/trac" =>
     109   
    90110                   ("trac" =>
    91111                     ("socket" => "/tmp/trac-fastcgi.sock",
    92                       "bin-path" => "/path/to/cgi-bin/trac.fcgi",
     112                      "bin-path" => fcgi_binary,
    93113                      "check-local" => "disable",
    94114                      "bin-environment" =>
     
    108128                   ("first" =>
    109129                    ("socket" => "/tmp/trac-fastcgi-first.sock",
    110                      "bin-path" => "/path/to/cgi-bin/trac.fcgi",
     130                     "bin-path" => fcgi_binary,
    111131                     "check-local" => "disable",
    112132                     "bin-environment" =>
     
    117137                    ("second" =>
    118138                    ("socket" => "/tmp/trac-fastcgi-second.sock",
    119                      "bin-path" => "/path/to/cgi-bin/trac.fcgi",
     139                     "bin-path" => fcgi_binary,
    120140                     "check-local" => "disable",
    121141                     "bin-environment" =>
     
    131151if both are running from the same `trac.fcgi` script.
    132152{{{
    133 #!html
    134 <p style="background: #fdc; border: 2px solid #d00; font-style: italic; padding: 0 .5em; margin: 1em 0;">
    135 <strong>Note from c00i90wn:</strong> It's very important the order on which server.modules are loaded, if mod_auth is not loaded <strong>BEFORE</strong> mod_fastcgi, then the server will fail to authenticate the user.
    136 </p>
     153#!div class=important
     154'''Note''' It's very important the order on which server.modules are loaded, if mod_auth is not loaded '''BEFORE''' mod_fastcgi, then the server will fail to authenticate the user.
    137155}}}
    138156For authentication you should enable mod_auth in lighttpd.conf 'server.modules', select auth.backend and auth rules:
     
    193211                   ("trac" =>
    194212                     ("socket" => "/tmp/trac-fastcgi.sock",
    195                       "bin-path" => "/path/to/cgi-bin/trac.fcgi",
     213                      "bin-path" => fcgi_binary,
    196214                      "check-local" => "disable",
    197215                      "bin-environment" =>
     
    212230                        (
    213231                          "socket" => "/tmp/trac.sock",
    214                           "bin-path" => "/path/to/cgi-bin/trac.fcgi",
     232                          "bin-path" => fcgi_binary,
    215233                          "check-local" => "disable",
    216234                          "bin-environment" =>
     
    238256                   ("trac" =>
    239257                     ("socket" => "/tmp/trac-fastcgi.sock",
    240                       "bin-path" => "/path/to/cgi-bin/trac.fcgi",
     258                      "bin-path" => fcgi_binary,
    241259                      "check-local" => "disable",
    242260                      "bin-environment" =>
     
    247265                 )
    248266}}}
    249 For details about languages specification see TracFaq question 2.13.
     267For details about languages specification see [trac:TracFaq TracFaq] question 2.13.
    250268
    251269Other important information like [http://trac.lighttpd.net/trac/wiki/TracInstall this updated TracInstall page], [wiki:TracCgi#MappingStaticResources and this] are useful for non-fastcgi specific installation aspects.
     
    260278
    261279
    262 == Simple LiteSpeed Configuration ==
     280== Simple !LiteSpeed Configuration ==
    263281
    264282The FastCGI front-end was developed primarily for use with alternative webservers, such as [http://www.litespeedtech.com/ LiteSpeed].
    265283
    266 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.
     284!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.
    267285
    268286Setup
     
    321339}}}
    322340
    323 7) Restart LiteSpeed, “lswsctrl restart”, and access your new Trac project at:
     3417) Restart !LiteSpeed, “lswsctrl restart”, and access your new Trac project at:
    324342
    325343{{{
     
    327345}}}
    328346
     347=== Simple Nginx Configuration ===
     348
     3491) Nginx configuration snippet - confirmed to work on 0.6.32
     350{{{
     351    server {
     352        listen       10.9.8.7:443;
     353        server_name  trac.example;
     354
     355        ssl                  on;
     356        ssl_certificate      /etc/ssl/trac.example.crt;
     357        ssl_certificate_key  /etc/ssl/trac.example.key;
     358
     359        ssl_session_timeout  5m;
     360
     361        ssl_protocols  SSLv2 SSLv3 TLSv1;
     362        ssl_ciphers  ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP;
     363        ssl_prefer_server_ciphers   on;
     364
     365        # (Or ``^/some/prefix/(.*)``.
     366        if ($uri ~ ^/(.*)) {
     367             set $path_info /$1;
     368        }
     369
     370        # You can copy this whole location to ``location [/some/prefix]/login``
     371        # and remove the auth entries below if you want Trac to enforce
     372        # authorization where appropriate instead of needing to authenticate
     373        # for accessing the whole site.
     374        # (Or ``location /some/prefix``.)
     375        location / {
     376            auth_basic            "trac realm";
     377            auth_basic_user_file /home/trac/htpasswd;
     378
     379            # socket address
     380            fastcgi_pass   unix:/home/trac/run/instance.sock;
     381
     382            # python - wsgi specific
     383            fastcgi_param HTTPS on;
     384
     385            ## WSGI REQUIRED VARIABLES
     386            # WSGI application name - trac instance prefix.
     387            # (Or ``fastcgi_param  SCRIPT_NAME  /some/prefix``.)
     388            fastcgi_param  SCRIPT_NAME        "";
     389            fastcgi_param  PATH_INFO          $path_info;
     390
     391            ## WSGI NEEDED VARIABLES - trac warns about them
     392            fastcgi_param  REQUEST_METHOD     $request_method;
     393            fastcgi_param  SERVER_NAME        $server_name;
     394            fastcgi_param  SERVER_PORT        $server_port;
     395            fastcgi_param  SERVER_PROTOCOL    $server_protocol;
     396
     397            # for authentication to work
     398            fastcgi_param  AUTH_USER          $remote_user;
     399            fastcgi_param  REMOTE_USER        $remote_user;
     400        }
     401    }
     402}}}
     403
     4042) Modified trac.fcgi:
     405
     406{{{
     407#!/usr/bin/env python
     408import os
     409sockaddr = '/home/trac/run/instance.sock'
     410os.environ['TRAC_ENV'] = '/home/trac/instance'
     411
     412try:
     413     from trac.web.main import dispatch_request
     414     import trac.web._fcgi
     415
     416     fcgiserv = trac.web._fcgi.WSGIServer(dispatch_request,
     417          bindAddress = sockaddr, umask = 7)
     418     fcgiserv.run()
     419
     420except SystemExit:
     421    raise
     422except Exception, e:
     423    print 'Content-Type: text/plain\r\n\r\n',
     424    print 'Oops...'
     425    print
     426    print 'Trac detected an internal error:'
     427    print
     428    print e
     429    print
     430    import traceback
     431    import StringIO
     432    tb = StringIO.StringIO()
     433    traceback.print_exc(file=tb)
     434    print tb.getvalue()
     435
     436}}}
     437
     4383) reload nginx and launch trac.fcgi like that:
     439
     440{{{
     441trac@trac.example ~ $ ./trac-standalone-fcgi.py
     442}}}
     443
     444The above assumes that:
     445 * There is a user named 'trac' for running trac instances and keeping trac environments in its home directory.
     446 * /home/trac/instance contains a trac environment
     447 * /home/trac/htpasswd contains authentication information
     448 * /home/trac/run is owned by the same group the nginx runs under
     449  * and if your system is Linux the /home/trac/run has setgid bit set (chmod g+s run)
     450  * and patch from ticket #T7239 is applied, or you'll have to fix the socket file permissions every time
     451
     452Unfortunately nginx does not support variable expansion in fastcgi_pass directive.
     453Thus it is not possible to serve multiple trac instances from one server block.
     454
     455If you worry enough about security, run trac instances under separate users.
     456
     457Another way to run trac as a FCGI external application is offered in ticket #T6224
     458
    329459----
    330 See also TracCgi, TracModPython, TracInstall, TracGuide
     460See also:  TracGuide, TracInstall, [wiki:TracModWSGI ModWSGI], [wiki:TracCgi CGI], [wiki:TracModPython ModPython], [trac:TracNginxRecipe TracNginxRecipe]