Edgewall Software

Changes between Version 51 and Version 52 of TracFastCgi


Ignore:
Timestamp:
Dec 15, 2008, 5:46:43 PM (15 years ago)
Author:
taher@…
Comment:

The recipe has screenshots, sorry if it can't be more readable. It will be released with the next Cherokee version (under http://cherokee-project.com/doc/cookbook_trac.html)

Legend:

Unmodified
Added
Removed
Modified
  • TracFastCgi

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