You can't have the last portion of the path identical between the projects since Trac uses that name to keep the URLs of the
different projects unique. So if you use /project1/path/to and /project2/path/to, you will only see the second project.

An alternative way to serve multiple projects is to specify a parent directory in which each subdirectory is a Trac project, using the -e option. The example above could be rewritten:

$ tracd -p 8080 -e /path/to

Using Authentication

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.

Support for Basic authentication was added in version 0.9.

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

How to set up an htdigest password file

If you have Apache available, you can use the htdigest command to generate the password file. Type 'htdigest' to get some usage instructions, or read this page from the Apache manual to get precise instructions. You'll be prompted for a password to enter for each user that you create. For the name of the password file, you can use whatever you like, but if you use something like users.htdigest it will remind you what the file contains. As a suggestion, put it in your <projectname>/conf folder along with the trac.ini file.

Note that you can start tracd without the --auth argument, but if you click on the Login link you will get an error.

Generating Passwords Without Apache

If you don't have Apache available, you can use this simple Python script to generate your passwords:

Note: If you use the above script you must use the --auth option to tracd, not --basic-auth, and you must set the realm in the --auth value to 'trac' (without the quotes). Example usage (assuming you saved the script as trac-digest.py):

Tips

Serving static content

If tracd is the only webserver used for the project,
it can also be used to distribute static content
(tarballs, Doxygen documentation, etc.)

This static content should be put in the $TRAC_ENV/htdocs folder,
and is accessed by URLs like <project_URL>/chrome/site/....

Example: given a $TRAC_ENV/htdocs/software-0.1.tar.gz file,
the corresponding relative URL would be /<project_name>/chrome/site/software-0.1.tar.gz,
which in turn can be written using the relative link syntax
in the Wiki: [/<project_name>/chrome/site/software-0.1.tar.gz]

The development version of Trac supports a new htdocs:TracLinks
syntax for the above. With this, the example link above can be written simply
htdocs:software-0.1.tar.gz.