| 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]. |
| 46 | | But neither of these will work for `mod_fcgid`. A similar but partial |
| 47 | | solution for `mod_fcgid` is: |
| | 39 | ==== setup with `mod_fcgid` ==== |
| | 40 | Configure `ScriptAlias` (see TracCgi for details), but call `trac.fcgi` |
| | 41 | instead of `trac.cgi`. Note that slash at the end - it is important. |
| | 42 | {{{ |
| | 43 | ScriptAlias /trac /path/to/www/trac/cgi-bin/trac.fcgi/ |
| | 44 | }}} |
| | 45 | |
| | 46 | To setup Trac environment for `mod_fcgid` it is necessary to use |
| | 47 | `DefaultInitEnv` directive. It cannot be used in `Directory` or |
| | 48 | `Location` context, so if you need to support multiple projects, try |
| | 49 | alternative environment setup below. |
| | 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.: |
| | 54 | |
| | 55 | ==== alternative environment setup ==== |
| | 56 | A better method to specify path to Trac environment it to embed the path |
| | 57 | into `trac.fcgi` script itself. That doesn't require configuration of server |
| | 58 | environment variables, works for both FastCgi modules |
| | 59 | (and for [http://www.lighttpd.net/ lighttpd] and CGI as well): |
| 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. |
| | 70 | With this method different projects can be supported by using different |
| | 71 | `.fcgi` scripts with different `ScriptAliases`. |
| | 72 | |
| | 73 | See [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: |
| | 74 | {{{ |
| | 75 | ScriptAlias / /srv/tracsite/cgi-bin/trac.fcgi/ |
| | 76 | }}} |
| | 77 | |
| | 78 | == Simple Cherokee Configuration == |
| | 79 | |
| | 80 | The configuration on Cherokee's side is quite simple. You will only need to know that you can spawn Trac as an SCGI process. |
| | 81 | You can either start it manually, or better yet, automatically by letting Cherokee spawn the server whenever it is down. |
| | 82 | First set up an information source in cherokee-admin with a local interpreter. |
| | 83 | |
| | 84 | {{{ |
| | 85 | Host: |
| | 86 | localhost:4433 |
| | 87 | |
| | 88 | Interpreter: |
| | 89 | /usr/bin/tracd —single-env —daemonize —protocol=scgi —hostname=localhost —port=4433 /path/to/project/ |
| | 90 | }}} |
| | 91 | |
| | 92 | If 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 | |
| | 94 | After 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. |
| | 95 | The 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/'' |
| | 96 | |
| | 97 | Note:\\ |
| | 98 | If the tracd process fails to start up, and cherokee displays a 503 error page, you might be missing the [http://trac.saddi.com/flup python-flup] package.\\ |
| | 99 | Python-flup is a dependency which provides trac with SCGI capability. You can install it on debian based systems with: |
| | 100 | {{{ |
| | 101 | sudo apt-get install python-flup |
| | 102 | }}} |
| 257 | | 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. |
| 258 | | |
| 259 | | Setup |
| 260 | | |
| 261 | | 1) Please make sure you have first have a working install of a Trac project. Test install with “tracd” first. |
| 262 | | |
| 263 | | 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: |
| | 293 | !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. |
| | 294 | |
| | 295 | === Setup === |
| | 296 | |
| | 297 | 1. Please make sure you have first have a working install of a Trac project. Test install with “tracd” first. |
| | 298 | |
| | 299 | 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: |
| | 356 | == Simple Nginx Configuration == |
| | 357 | |
| | 358 | 1. Nginx configuration snippet - confirmed to work on 0.6.32 |
| | 359 | {{{ |
| | 360 | server { |
| | 361 | listen 10.9.8.7:443; |
| | 362 | server_name trac.example; |
| | 363 | |
| | 364 | ssl on; |
| | 365 | ssl_certificate /etc/ssl/trac.example.crt; |
| | 366 | ssl_certificate_key /etc/ssl/trac.example.key; |
| | 367 | |
| | 368 | ssl_session_timeout 5m; |
| | 369 | |
| | 370 | ssl_protocols SSLv2 SSLv3 TLSv1; |
| | 371 | ssl_ciphers ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP; |
| | 372 | ssl_prefer_server_ciphers on; |
| | 373 | |
| | 374 | # (Or ``^/some/prefix/(.*)``. |
| | 375 | if ($uri ~ ^/(.*)) { |
| | 376 | set $path_info /$1; |
| | 377 | } |
| | 378 | |
| | 379 | # You can copy this whole location to ``location [/some/prefix]/login`` |
| | 380 | # and remove the auth entries below if you want Trac to enforce |
| | 381 | # authorization where appropriate instead of needing to authenticate |
| | 382 | # for accessing the whole site. |
| | 383 | # (Or ``location /some/prefix``.) |
| | 384 | location / { |
| | 385 | auth_basic "trac realm"; |
| | 386 | auth_basic_user_file /home/trac/htpasswd; |
| | 387 | |
| | 388 | # socket address |
| | 389 | fastcgi_pass unix:/home/trac/run/instance.sock; |
| | 390 | |
| | 391 | # python - wsgi specific |
| | 392 | fastcgi_param HTTPS on; |
| | 393 | |
| | 394 | ## WSGI REQUIRED VARIABLES |
| | 395 | # WSGI application name - trac instance prefix. |
| | 396 | # (Or ``fastcgi_param SCRIPT_NAME /some/prefix``.) |
| | 397 | fastcgi_param SCRIPT_NAME ""; |
| | 398 | fastcgi_param PATH_INFO $path_info; |
| | 399 | |
| | 400 | ## WSGI NEEDED VARIABLES - trac warns about them |
| | 401 | fastcgi_param REQUEST_METHOD $request_method; |
| | 402 | fastcgi_param SERVER_NAME $server_name; |
| | 403 | fastcgi_param SERVER_PORT $server_port; |
| | 404 | fastcgi_param SERVER_PROTOCOL $server_protocol; |
| | 405 | fastcgi_param QUERY_STRING $query_string; |
| | 406 | |
| | 407 | # for authentication to work |
| | 408 | fastcgi_param AUTH_USER $remote_user; |
| | 409 | fastcgi_param REMOTE_USER $remote_user; |
| | 410 | } |
| | 411 | } |
| | 412 | }}} |
| | 413 | |
| | 414 | 2. Modified trac.fcgi: |
| | 415 | |
| | 416 | {{{ |
| | 417 | #!/usr/bin/env python |
| | 418 | import os |
| | 419 | sockaddr = '/home/trac/run/instance.sock' |
| | 420 | os.environ['TRAC_ENV'] = '/home/trac/instance' |
| | 421 | |
| | 422 | try: |
| | 423 | from trac.web.main import dispatch_request |
| | 424 | import trac.web._fcgi |
| | 425 | |
| | 426 | fcgiserv = trac.web._fcgi.WSGIServer(dispatch_request, |
| | 427 | bindAddress = sockaddr, umask = 7) |
| | 428 | fcgiserv.run() |
| | 429 | |
| | 430 | except SystemExit: |
| | 431 | raise |
| | 432 | except Exception, e: |
| | 433 | print 'Content-Type: text/plain\r\n\r\n', |
| | 434 | print 'Oops...' |
| | 435 | print |
| | 436 | print 'Trac detected an internal error:' |
| | 437 | print |
| | 438 | print e |
| | 439 | print |
| | 440 | import traceback |
| | 441 | import StringIO |
| | 442 | tb = StringIO.StringIO() |
| | 443 | traceback.print_exc(file=tb) |
| | 444 | print tb.getvalue() |
| | 445 | |
| | 446 | }}} |
| | 447 | |
| | 448 | 3. reload nginx and launch trac.fcgi like that: |
| | 449 | |
| | 450 | {{{ |
| | 451 | trac@trac.example ~ $ ./trac-standalone-fcgi.py |
| | 452 | }}} |
| | 453 | |
| | 454 | The above assumes that: |
| | 455 | * There is a user named 'trac' for running trac instances and keeping trac environments in its home directory. |
| | 456 | * `/home/trac/instance` contains a trac environment |
| | 457 | * `/home/trac/htpasswd` contains authentication information |
| | 458 | * `/home/trac/run` is owned by the same group the nginx runs under |
| | 459 | * and if your system is Linux the `/home/trac/run` has setgid bit set (`chmod g+s run`) |
| | 460 | * and patch from ticket #T7239 is applied, or you'll have to fix the socket file permissions every time |
| | 461 | |
| | 462 | Unfortunately nginx does not support variable expansion in fastcgi_pass directive. |
| | 463 | Thus it is not possible to serve multiple trac instances from one server block. |
| | 464 | |
| | 465 | If you worry enough about security, run trac instances under separate users. |
| | 466 | |
| | 467 | Another way to run trac as a FCGI external application is offered in ticket #T6224 |
| | 468 | |
