| 5 | | [http://www.fastcgi.com/ 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 much wider variety of web servers. |
| 6 | | |
| 7 | | Note that unlike mod_python, FastCGI supports [http://httpd.apache.org/docs/suexec.html Apache SuEXEC], i.e. run with different permissions than web server running with (`mod_wsgi` supports the `WSGIDaemonProcess` with user / group parameters to achieve the same effect). |
| | 6 | [http://www.fastcgi.com/ 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 [http://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. |
| 50 | | === Set up with `mod_fcgid` === |
| 51 | | Configure `ScriptAlias` (see TracCgi for details), but call `trac.fcgi` |
| 52 | | instead of `trac.cgi`. Note that slash at the end - it is important. |
| 53 | | {{{ |
| | 48 | You can also specify the `PYTHON_EGG_CACHE` environment variable using a second `-initial-env` directive: |
| | 49 | {{{#!apache |
| | 50 | FastCgiConfig -initial-env TRAC_ENV=/var/lib/trac \ |
| | 51 | -initial-env PYTHON_EGG_CACHE=/var/lib/trac/plugin-cache |
| | 52 | }}} |
| | 53 | |
| | 54 | === Set up with `mod_fcgid` |
| | 55 | |
| | 56 | Configure `ScriptAlias` (see TracCgi for details), but call `trac.fcgi` instead of `trac.cgi`: |
| | 57 | {{{#!apache |
| 57 | | To set up Trac environment for `mod_fcgid` it is necessary to use |
| 58 | | `DefaultInitEnv` directive. It cannot be used in `Directory` or |
| 59 | | `Location` context, so if you need to support multiple projects, try |
| 60 | | alternative environment setup below. |
| 61 | | |
| 62 | | {{{ |
| | 61 | Note the slash at the end. |
| | 62 | |
| | 63 | To set up Trac environment for `mod_fcgid` it is necessary to use `DefaultInitEnv` directive. It cannot be used in `Directory` or `Location` context, so if you need to support multiple projects, try the alternative environment setup below: |
| | 64 | {{{#!apache |
| 66 | | === alternative environment setup === |
| 67 | | A better method to specify path to Trac environment is to embed the path |
| 68 | | into `trac.fcgi` script itself. That doesn't require configuration of server |
| 69 | | environment variables, works for both FastCgi modules |
| 70 | | (and for [http://www.lighttpd.net/ lighttpd] and CGI as well): |
| 71 | | {{{ |
| | 68 | === Alternative environment setup |
| | 69 | |
| | 70 | A better method to specify the path to the Trac environment is to embed the path into `trac.fcgi` script itself. That doesn't require configuration of the server environment variables, works for both [trac:FastCgi] modules as well as for [http://www.lighttpd.net/ lighttpd] and CGI: |
| | 71 | {{{#!python |
| 89 | | == Simple Cherokee Configuration == |
| 90 | | |
| 91 | | The configuration on Cherokee's side is quite simple. You will only need to know that you can spawn Trac as an SCGI process. |
| 92 | | You can either start it manually, or better yet, automatically by letting Cherokee spawn the server whenever it is down. |
| 93 | | First set up an information source in cherokee-admin with a local interpreter. |
| | 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: |
| 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:\\ |
| 109 | | 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.\\ |
| 110 | | Python-flup is a dependency which provides trac with SCGI capability. You can install it on debian based systems with: |
| 111 | | {{{ |
| | 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 [http://trac.saddi.com/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 |
| 115 | | |
| 116 | | == Simple Lighttpd Configuration == |
| 117 | | |
| 118 | | The FastCGI front-end was developed primarily for use with alternative webservers, such as [http://www.lighttpd.net/ lighttpd]. |
| 119 | | |
| 120 | | lighttpd is a secure, fast, compliant and very flexible web-server that has been optimized for high-performance |
| 121 | | environments. It has a very low memory footprint compared to other web servers and takes care of CPU load. |
| 122 | | |
| 123 | | For using `trac.fcgi`(prior to 0.11) / fcgi_frontend.py (0.11) with lighttpd add the following to your lighttpd.conf: |
| | 113 | == Lighttpd Configuration |
| | 114 | |
| | 115 | The FastCGI front-end was developed primarily for use with alternative webservers, such as [http://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: |
| 140 | | Note that you will need to add a new entry to `fastcgi.server` for each separate Trac instance that you wish to run. Alternatively, you may use the `TRAC_ENV_PARENT_DIR` variable instead of `TRAC_ENV` as described above, |
| 141 | | and you may set one of the two in `trac.fcgi` instead of in `lighttpd.conf` |
| 142 | | using `bin-environment` (as in the section above on Apache configuration). |
| 143 | | |
| 144 | | Note that lighttpd has a bug related to 'SCRIPT_NAME' and 'PATH_INFO' when the uri of fastcgi.server is '/' instead of '/trac' in this example (see [trac:#2418]). This is fixed in lighttpd 1.5, and under lighttpd 1.4.23 or later the workaround is to add `"fix-root-scriptname" => "enable"` as a parameter of fastcgi.server. |
| | 136 | Note that you will need to add a new entry to `fastcgi.server` for each separate Trac instance that you wish to run. Alternatively, you may use the `TRAC_ENV_PARENT_DIR` variable instead of `TRAC_ENV` as described above, and you may set one of the two in `trac.fcgi` instead of in `lighttpd.conf` using `bin-environment`, as in the section above on Apache configuration. |
| | 137 | |
| | 138 | Note that Lighttpd has a bug related to 'SCRIPT_NAME' and 'PATH_INFO' when the uri of fastcgi.server is '/' instead of '/trac' in this example (see [trac:#2418]). This is fixed in Lighttpd 1.5, and under Lighttpd 1.4.23 or later the workaround is to add `"fix-root-scriptname" => "enable"` as a parameter of fastcgi.server. |
| 168 | | Note that field values are different. If you prefer setting the environment |
| 169 | | variables in the `.fcgi` scripts, then copy/rename `trac.fcgi`, e.g., to |
| 170 | | `first.fcgi` and `second.fcgi`, and reference them in the above settings. |
| 171 | | Note that the above will result in different processes in any event, even |
| 172 | | if both are running from the same `trac.fcgi` script. |
| 173 | | |
| 174 | | {{{ |
| 175 | | #!div class=important |
| 176 | | '''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. |
| | 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. |
| 293 | | ] |
| 294 | | |
| 295 | | Relaunch lighttpd, and browse to `http://yourhost.example.org/trac` to access Trac. |
| 296 | | |
| 297 | | Note about running lighttpd with reduced permissions: |
| 298 | | |
| 299 | | 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. |
| 300 | | |
| 301 | | |
| 302 | | == Simple !LiteSpeed Configuration == |
| | 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 |
| 360 | | |
| 361 | | 7. Restart !LiteSpeed, “lswsctrl restart”, and access your new Trac project at: |
| 362 | | |
| 363 | | {{{ |
| 364 | | http://yourdomain.com/trac/ |
| 365 | | }}} |
| 366 | | |
| 367 | | |
| 368 | | == Simple Nginx Configuration == |
| 369 | | |
| 370 | | Nginx is able to communicate with FastCGI processes, but can not spawn them. So you need to start FastCGI server for Trac separately. |
| | 339 | 1. Restart !LiteSpeed: `lswsctrl restart`, and access your new Trac project at {{{http://yourdomain.com/trac/}}}. |
| | 340 | |
| | 341 | == Nginx Configuration |
| | 342 | |
| | 343 | [http://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. |
| 478 | | * and patch from ticket #T7239 is applied, or you'll have to fix the socket file permissions every time |
| 479 | | |
| 480 | | Unfortunately nginx does not support variable expansion in fastcgi_pass directive. |
| 481 | | Thus it is not possible to serve multiple trac instances from one server block. |
| 482 | | |
| 483 | | If you worry enough about security, run trac instances under separate users. |
| 484 | | |
| 485 | | Another way to run trac as a FCGI external application is offered in ticket #T6224 |
| | 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]. |
