| 1 | | = Trac with FastCGI = |
| 2 | | |
| 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 | | }}} |
| 11 | | |
| 12 | | == Simple Apache configuration == |
| 13 | | |
| 14 | | There 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: |
| 21 | | {{{ |
| | 1 | = Trac with FastCGI |
| | 2 | |
| | 3 | [[TracGuideToc]] |
| | 4 | [[PageOutline(2-5, Contents, floated)]] |
| | 5 | |
| | 6 | [https://fastcgi-archives.github.io FastCGI] interface allows Trac to remain resident much like with [wiki:TracModPython mod_python] or [wiki:TracModWSGI mod_wsgi]. It is faster than external CGI interfaces which must start a new process for each request. Additionally, it is supported by a much wider variety of web servers. |
| | 7 | |
| | 8 | Note that unlike mod_python, FastCGI supports [https://httpd.apache.org/docs/suexec.html Apache SuEXEC], ie run with different permissions than the web server runs with. `mod_wsgi` supports the `WSGIDaemonProcess` with user / group parameters to achieve the same effect. |
| | 9 | |
| | 10 | '''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]/[trac:TracOnWindowsIisAjp ISAPI]. |
| | 11 | |
| | 12 | == Apache configuration |
| | 13 | |
| | 14 | There are two FastCGI modules commonly available for Apache: `mod_fastcgi` and `mod_fcgid` (preferred). The latter is more up-to-date. |
| | 15 | |
| | 16 | The following sections focus on the FCGI specific setup, see also [wiki:TracModWSGI#ConfiguringAuthentication] for configuring the authentication in Apache. |
| | 17 | |
| | 18 | Regardless of which cgi module is used, be sure the web server has executable permissions on the cgi-bin folder. While FastCGI will throw specific permissions errors, mod_fcgid will throw an ambiguous error if this has not been done: `Connection reset by peer: mod_fcgid: error reading data from FastCGI server`. |
| | 19 | |
| | 20 | === Set up with `mod_fastcgi` |
| | 21 | |
| | 22 | `mod_fastcgi` uses `FastCgiIpcDir` and `FastCgiConfig` directives that should be added to an appropriate Apache configuration file: |
| | 23 | {{{#!apache |
| 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 | | |
| 71 | | == Simple Lighttpd Configuration == |
| 72 | | |
| 73 | | The FastCGI front-end was developed primarily for use with alternative webservers, such as [http://www.lighttpd.net/ lighttpd]. |
| 74 | | |
| 75 | | lighttpd is a secure, fast, compliant and very flexible web-server that has been optimized for high-performance |
| 76 | | environments. It has a very low memory footprint compared to other web servers and takes care of CPU load. |
| 77 | | |
| 78 | | For using `trac.fcgi` with lighttpd add the following to your lighttpd.conf: |
| 79 | | {{{ |
| | 82 | With this method different projects can be supported by using different `.fcgi` scripts with different `ScriptAliases`. |
| | 83 | |
| | 84 | 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: |
| | 85 | {{{#!apache |
| | 86 | ScriptAlias / /srv/tracsite/cgi-bin/trac.fcgi/ |
| | 87 | }}} |
| | 88 | |
| | 89 | == Cherokee Configuration |
| | 90 | |
| | 91 | Configuring [http://cherokee-project.com/ Cherokee] with Trac is straightforward, if you spawn Trac as an SCGI process. You can either start it manually, or better yet, automatically by letting Cherokee spawn the server whenever it is down. |
| | 92 | |
| | 93 | First set up an information source in cherokee-admin with a local interpreter: |
| | 94 | |
| | 95 | {{{ |
| | 96 | Host: |
| | 97 | localhost:4433 |
| | 98 | |
| | 99 | Interpreter: |
| | 100 | /usr/bin/tracd —single-env —daemonize —protocol=scgi —hostname=localhost —port=4433 /path/to/project/ |
| | 101 | }}} |
| | 102 | |
| | 103 | 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''. |
| | 104 | |
| | 105 | 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. |
| | 106 | 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 ''/common'' and just set it to the ''Static files'' handler and with a ''Document root'' that points to the appropriate files: ''$TRAC_LOCAL/htdocs/'' (where $TRAC_LOCAL is a directory defined by the user or the system administrator to place local Trac resources). |
| | 107 | |
| | 108 | '''Note:''' If the tracd process fails to start up, and Cherokee displays a 503 error page, you might be missing the [https://www.saddi.com/software/flup/ python-flup] package ([trac:#9903]). Python-flup is a dependency which provides Trac with SCGI capability. You can install it on Debian based systems with: |
| | 109 | {{{#!sh |
| | 110 | sudo apt-get install python-flup |
| | 111 | }}} |
| | 112 | |
| | 113 | == Lighttpd Configuration |
| | 114 | |
| | 115 | The FastCGI front-end was developed primarily for use with alternative webservers, such as [https://www.lighttpd.net/ Lighttpd]. |
| | 116 | |
| | 117 | Lighttpd is a secure, fast, compliant and very flexible web-server that has been optimized for high-performance environments. It has a very low memory footprint compared to other web servers and takes care of CPU load. |
| | 118 | |
| | 119 | For using `trac.fcgi`(prior to 0.11) / fcgi_frontend.py (0.11) with Lighttpd add the following to your lighttpd.conf: |
| | 120 | {{{ |
| | 121 | #var.fcgi_binary="/usr/bin/python /path/to/fcgi_frontend.py" # 0.11 if installed with easy_setup, it is inside the egg directory |
| | 122 | var.fcgi_binary="/path/to/cgi-bin/trac.fcgi" # 0.10 name of prior fcgi executable |
| 118 | | Note that field values are different. If you prefer setting the environment |
| 119 | | variables in the `.fcgi` scripts, then copy/rename `trac.fcgi`, e.g., to |
| 120 | | `first.fcgi` and `second.fcgi`, and reference them in the above settings. |
| 121 | | Note that the above will result in different processes in any event, even |
| 122 | | if both are running from the same `trac.fcgi` script. |
| 123 | | {{{ |
| 124 | | #!html |
| 125 | | <p style="background: #fdc; border: 2px solid #d00; font-style: italic; padding: 0 .5em; margin: 1em 0;"> |
| 126 | | <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. |
| 127 | | </p> |
| 128 | | }}} |
| | 162 | |
| | 163 | Note that the field values are different. If you prefer setting the environment variables in the `.fcgi` scripts, then copy/rename `trac.fcgi`, eg to `first.fcgi` and `second.fcgi`, and reference them in the above settings. |
| | 164 | Note that the above will result in different processes in any event, even if both are running from the same `trac.fcgi` script. |
| | 165 | |
| | 166 | {{{#!div class=important |
| | 167 | '''Note:''' The order in which the server.modules are loaded is very important: if mod_auth is not loaded '''before''' mod_fastcgi, then the server will fail to authenticate the user. |
| | 168 | }}} |
| | 169 | |
| 240 | | For details about languages specification see TracFaq question 2.13. |
| 241 | | |
| 242 | | Other 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. |
| 243 | | |
| 244 | | If you use trac-0.9, read [http://lists.edgewall.com/archive/trac/2005-November/005311.html about small bug] |
| 245 | | |
| 246 | | Relaunch lighttpd, and browse to `http://yourhost.example.org/trac` to access Trac. |
| 247 | | |
| 248 | | Note about running lighttpd with reduced permissions: |
| 249 | | |
| 250 | | 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. |
| 251 | | |
| 252 | | |
| 253 | | == Simple LiteSpeed Configuration == |
| 254 | | |
| 255 | | The FastCGI front-end was developed primarily for use with alternative webservers, such as [http://www.litespeedtech.com/ LiteSpeed]. |
| 256 | | |
| 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: |
| 264 | | |
| | 283 | |
| | 284 | For details about languages specification see [trac:TracFaq TracFaq] question 2.13. |
| | 285 | |
| | 286 | Other important information like the [wiki:TracInstall#MappingStaticResources mapping static resources advices] are useful for non-fastcgi specific installation aspects. |
| | 287 | |
| | 288 | Relaunch Lighttpd and browse to `http://yourhost.example.org/trac` to access Trac. |
| | 289 | |
| | 290 | 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. |
| | 291 | |
| | 292 | == !LiteSpeed Configuration |
| | 293 | |
| | 294 | The FastCGI front-end was developed primarily for use with alternative webservers, such as [https://www.litespeedtech.com/ LiteSpeed]. |
| | 295 | |
| | 296 | !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. |
| | 297 | |
| | 298 | 1. Please make sure you have a working install of a Trac project. Test install with "tracd" first. |
| | 299 | 1. 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: |
| 313 | | |
| 314 | | 7) Restart LiteSpeed, “lswsctrl restart”, and access your new Trac project at: |
| 315 | | |
| 316 | | {{{ |
| 317 | | http://yourdomain.com/trac/ |
| 318 | | }}} |
| | 339 | 1. Restart !LiteSpeed: `lswsctrl restart`, and access your new Trac project at {{{http://yourdomain.com/trac/}}}. |
| | 340 | |
| | 341 | == Nginx Configuration |
| | 342 | |
| | 343 | [https://nginx.org/en/ Nginx] is able to communicate with FastCGI processes, but can not spawn them. So you need to start FastCGI server for Trac separately. |
| | 344 | |
| | 345 | 1. Nginx configuration with basic authentication handled by Nginx - confirmed to work on 0.6.32 |
| | 346 | {{{#!nginx |
| | 347 | server { |
| | 348 | listen 10.9.8.7:443; |
| | 349 | server_name trac.example; |
| | 350 | |
| | 351 | ssl on; |
| | 352 | ssl_certificate /etc/ssl/trac.example.crt; |
| | 353 | ssl_certificate_key /etc/ssl/trac.example.key; |
| | 354 | |
| | 355 | ssl_session_timeout 5m; |
| | 356 | |
| | 357 | ssl_protocols SSLv2 SSLv3 TLSv1; |
| | 358 | ssl_ciphers ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP; |
| | 359 | ssl_prefer_server_ciphers on; |
| | 360 | |
| | 361 | # it makes sense to serve static resources through Nginx (or ``~ [/some/prefix]/chrome/(.*)``) |
| | 362 | location ~ /chrome/(.*) { |
| | 363 | alias /home/trac/instance/static/htdocs/$1; |
| | 364 | } |
| | 365 | |
| | 366 | # You can copy this whole location to ``location [/some/prefix](/login)`` |
| | 367 | # and remove the auth entries below if you want Trac to enforce |
| | 368 | # authorization where appropriate instead of needing to authenticate |
| | 369 | # for accessing the whole site. |
| | 370 | # (Or ``~ location /some/prefix(/.*)``.) |
| | 371 | location ~ (/.*) { |
| | 372 | auth_basic "trac realm"; |
| | 373 | auth_basic_user_file /home/trac/htpasswd; |
| | 374 | |
| | 375 | # socket address |
| | 376 | fastcgi_pass unix:/home/trac/run/instance.sock; |
| | 377 | |
| | 378 | # python - wsgi specific |
| | 379 | fastcgi_param HTTPS on; |
| | 380 | |
| | 381 | ## WSGI REQUIRED VARIABLES |
| | 382 | # WSGI application name - trac instance prefix. |
| | 383 | # (Or ``fastcgi_param SCRIPT_NAME /some/prefix``.) |
| | 384 | fastcgi_param SCRIPT_NAME ""; |
| | 385 | fastcgi_param PATH_INFO $1; |
| | 386 | |
| | 387 | ## WSGI NEEDED VARIABLES - trac warns about them |
| | 388 | fastcgi_param REQUEST_METHOD $request_method; |
| | 389 | fastcgi_param SERVER_NAME $server_name; |
| | 390 | fastcgi_param SERVER_PORT $server_port; |
| | 391 | fastcgi_param SERVER_PROTOCOL $server_protocol; |
| | 392 | fastcgi_param QUERY_STRING $query_string; |
| | 393 | |
| | 394 | # For Nginx authentication to work - do not forget to comment these |
| | 395 | # lines if not using Nginx for authentication |
| | 396 | fastcgi_param AUTH_USER $remote_user; |
| | 397 | fastcgi_param REMOTE_USER $remote_user; |
| | 398 | |
| | 399 | # for ip to work |
| | 400 | fastcgi_param REMOTE_ADDR $remote_addr; |
| | 401 | |
| | 402 | # For attchments to work |
| | 403 | fastcgi_param CONTENT_TYPE $content_type; |
| | 404 | fastcgi_param CONTENT_LENGTH $content_length; |
| | 405 | } |
| | 406 | } |
| | 407 | }}} |
| | 408 | 1. Modified trac.fcgi: |
| | 409 | {{{#!python |
| | 410 | #!/usr/bin/env python |
| | 411 | import os |
| | 412 | sockaddr = '/home/trac/run/instance.sock' |
| | 413 | os.environ['TRAC_ENV'] = '/home/trac/instance' |
| | 414 | |
| | 415 | try: |
| | 416 | from trac.web.main import dispatch_request |
| | 417 | import trac.web._fcgi |
| | 418 | |
| | 419 | fcgiserv = trac.web._fcgi.WSGIServer(dispatch_request, |
| | 420 | bindAddress = sockaddr, umask = 7) |
| | 421 | fcgiserv.run() |
| | 422 | |
| | 423 | except SystemExit: |
| | 424 | raise |
| | 425 | except Exception, e: |
| | 426 | print 'Content-Type: text/plain\r\n\r\n', |
| | 427 | print 'Oops...' |
| | 428 | print |
| | 429 | print 'Trac detected an internal error:' |
| | 430 | print |
| | 431 | print e |
| | 432 | print |
| | 433 | import traceback |
| | 434 | import StringIO |
| | 435 | tb = StringIO.StringIO() |
| | 436 | traceback.print_exc(file=tb) |
| | 437 | print tb.getvalue() |
| | 438 | |
| | 439 | }}} |
| | 440 | 1. Reload nginx and launch trac.fcgi: |
| | 441 | {{{#!sh |
| | 442 | trac@trac.example ~ $ ./trac-standalone-fcgi.py |
| | 443 | }}} |
| | 444 | |
| | 445 | The above assumes that: |
| | 446 | * There is a user named 'trac' for running Trac instances and keeping Trac environments in its home directory |
| | 447 | * `/home/trac/instance` contains a Trac environment |
| | 448 | * `/home/trac/htpasswd` contains authentication information |
| | 449 | * `/home/trac/run` is owned by the same group the Nginx runs under |
| | 450 | * and if your system is Linux the `/home/trac/run` has setgid bit set (`chmod g+s run`) |
| | 451 | * and patch from [trac:#7239] is applied, or you'll have to fix the socket file permissions every time |
| | 452 | |
| | 453 | Unfortunately Nginx does not support variable expansion in fastcgi_pass directive. |
| | 454 | Thus it is not possible to serve multiple Trac instances from one server block. |
| | 455 | |
| | 456 | If you worry enough about security, run Trac instances under separate users. |
| | 457 | |
| | 458 | Another way to run Trac as a FCGI external application is offered in [trac:#6224]. |
