Legend:

Tracd is a lightweight standalone Trac web server. In most cases it's easier to setup and runs faster than the [wiki:TracCgi CGI script].

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 [wiki:TracModPython mod_python] version (and much faster than the [wiki:TracCgi CGI]).

9

10

== Cons ==

11

12

* Less features: Tracd implements a very simple web-server and is not as configurable as Apache HTTPD.

13

* No native HTTPS support: [http://www.rickk.com/sslwrap/ sslwrap] can be used instead,

14

or [http://lists.edgewall.com/archive/trac/2005-August/004381.html STUNNEL].

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

27

You can't have the last portion of the path identical between the projects since that's how trac keeps the URLs of the

28

different projects unique. So if you use /project1/path/to and /project2/path/to, you will only see the second project.

29

30

== Using Authentication ==

31

32

Tracd provides support for both Basic and Digest authentication. The default is to use Digest; to use Basic authentication, replace `--auth` with `--basic-auth` in the examples below, and omit the realm.

33

34

If the file `/path/to/users.htdigest` contain user accounts for project1 with the realm "mycompany.com", you'd use the following command-line to start tracd: