|Version 5 (modified by 15 years ago) ( diff ),|
This page documents the 1.4 (latest stable) release. Documentation for other releases can be found here.
Tracd is a lightweight stand-alone Trac server. In most cases it's easier to setup and runs faster than trac.cgi.
Note: tracd is still experimental.
- Fewer dependencies: You don't need to install apache or any other web-server.
- Fast: Should be as fast as the TracModPython version (much faster than the cgi).
- Less features: Tracd implements a very simple web-server and is not as configurable as apache.
- Only htdigest authentication: Tracd can currently only authenticate users against apache-htdigest files.
- No native https support: sslwrap can be used instead.
A single project on port 8080. (http://localhost:8080/)
$ tracd -p 8080 /path/to/project
$ tracd -p 8080 /path/to/project1 /path/to/project2
With htdigest authentication. The file /tmp/users.htdigest contain user accounts for project1 with the realm "mycompany.com".
$ tracd -p 8080 --auth project1,/tmp/users.htdigest,mycompany.com /path/to/project1
htdigest authentication can also be used for more than one project. The digest file can be shared:
$ tracd -p 8080 \ --auth project1,/tmp/users.htdigest,mycompany.com \ --auth project2,/tmp/users.htdigest,mycompany.com \ /path/to/project1 /path/to/project2
Tracd on Windows
tracd also works on Windows. But on that platform, the sensitivity on multithread issues is high. tracd is not (yet!) very robust in multithread mode, see for example #1401 and #1721 for some of the issues…
I recently found out that all the occasional problems (i.e. crashes) I had can be avoided by telling tracd to operate in single-threaded mode:
124 124 return auth['username'] 125 125 126 126 127 class TracHTTPServer( ThreadingMixIn,HTTPServer): 127 class TracHTTPServer(HTTPServer): 128 128 129 129 projects = None