| | 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 | == Pros == |
| | 6 | |
| | 7 | * Fewer dependencies: You don't need to install apache or any other web-server. |
| | 8 | * Fast: Should be as fast as the ModPython version (much faster than the cgi). |
| | 9 | |
| | 10 | == Cons == |
| | 11 | |
| | 12 | * Less features: Tracd implements a very simple web-server and is not as configurable as apache. |
| | 13 | * Only htdigest authentication: Tracd can currently only authenticate users against apache-htdigest files. |
| | 14 | * No native https support: [http://www.rickk.com/sslwrap/ sslwrap] can be used instead. |
| | 15 | |
| | 16 | == Usage examples == |
| | 17 | |
| | 18 | A single project on port 8080. (http://localhost:8080/) |
| | 19 | {{{ |
| | 20 | $ tracd -p 8080 /path/to/project |
| | 21 | }}} |
| | 22 | With more than one project. (http://localhost:8080/project1/ and http://localhost:8080/project2/) |
| | 23 | {{{ |
| | 24 | $ tracd -p 8080 /path/to/project1 /path/to/project2 |
| | 25 | }}} |
| | 26 | With htdigest authentication. The file /tmp/users.htdigest contain user accounts for project1 with the realm "mycompany.com". |
| | 27 | {{{ |
| | 28 | $ tracd -p 8080 --auth project1,/tmp/users.htdigest,mycompany.com /path/to/project1 |
| | 29 | }}} |
