| 1 | = Tracd = |
| 2 | |
| 3 | Tracd is a lightweight stand-alone Trac server. In most cases it's easier to setup and runs faster than trac.cgi. |
| 4 | |
| 5 | '''Note: tracd is still experimental.''' |
| 6 | |
| 7 | == Pros == |
| 8 | |
| 9 | * Fewer dependencies: You don't need to install apache or any other web-server. |
| 10 | * Fast: Should be as fast as the ModPython version (much faster than the cgi). |
| 11 | |
| 12 | == Cons == |
| 13 | |
| 14 | * Less features: Tracd implements a very simple web-server and is not as configurable as apache. |
| 15 | * Only htdigest authentication: Tracd can currently only authenticate users against apache-htdigest files. |
| 16 | * No native https support: [http://www.rickk.com/sslwrap/ sslwrap] can be used instead. |
| 17 | |
| 18 | == Usage examples == |
| 19 | |
| 20 | A single project on port 8080. (http://localhost:8080/) |
| 21 | {{{ |
| 22 | $ tracd -p 8080 /path/to/project |
| 23 | }}} |
| 24 | With more than one project. (http://localhost:8080/project1/ and http://localhost:8080/project2/) |
| 25 | {{{ |
| 26 | $ tracd -p 8080 /path/to/project1 /path/to/project2 |
| 27 | }}} |
| 28 | With htdigest authentication. The file /tmp/users.htdigest contain user accounts for project1 with the realm "mycompany.com". |
| 29 | {{{ |
| 30 | $ tracd -p 8080 --auth project1,/tmp/users.htdigest,mycompany.com /path/to/project1 |
| 31 | }}} |
| 32 | |
| 33 | |
| 34 | ---- |
| 35 | See also: TracGuide, TracInstall, TracModPython |