73 | | Configuration wanted. |
| 73 | The configuration on Cherokee's side is quite simple. You will only need to know that you can spawn Trac as an SCGI process. |
| 74 | You can either start it manually, or better yet, automatically by letting Cherokee spawn the server whenever it is down. |
| 75 | First set up an information source in cherokee-admin with a local interpreter. |
| 76 | |
| 77 | {{{ |
| 78 | Host: |
| 79 | localhost:4433 |
| 80 | |
| 81 | Interpreter: |
| 82 | /usr/bin/tracd —single-env —daemonize —protocol=scgi —hostname=localhost —port=4433 /path/to/project/ |
| 83 | }}} |
| 84 | |
| 85 | 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''. |
| 86 | |
| 87 | 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. |
| 88 | 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/'' |