| 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. |
| | 28 | 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 |
| | 29 | different projects unique. So if you use `/project1/path/to` and `/project2/path/to`, you will only see the second project. |
| | 30 | |
| | 31 | 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: |
| | 32 | {{{ |
| | 33 | $ tracd -p 8080 -e /path/to |
| | 34 | }}} |
| | 56 | |
| | 57 | Another way to share the digest file is to specify "*" |
| | 58 | for the project name: |
| | 59 | {{{ |
| | 60 | $ tracd -p 8080 \ |
| | 61 | --auth *,/path/to/users.htdigest,mycompany.com \ |
| | 62 | /path/to/project1 /path/to/project2 |
| | 63 | }}} |
| | 64 | |
| | 65 | == How to set up an htdigest password file == |
| | 66 | |
| | 67 | 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 [http://httpd.apache.org/docs/2.0/programs/htdigest.html 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 [TracIni trac.ini] file. |
| | 68 | |
| | 69 | Note that you can start tracd without the --auth argument, but if you click on the ''Login'' link you will get an error. |
| | 98 | 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): |
| | 99 | |
| | 100 | {{{ |
| | 101 | python trac-digest.py -u username -p password >> c:\digest.txt |
| | 102 | python tracd --port 8000 --auth proj_name,c:\digest.txt,trac c:\path\to\proj_name |
| | 103 | }}} |
| | 104 | |
| | 105 | == Tips == |
| | 106 | |
| | 107 | === Serving static content === |
| | 108 | |
| | 109 | If `tracd` is the only webserver used for the project, |
| | 110 | it can also be used to distribute static content |
| | 111 | (tarballs, Doxygen documentation, etc.) |
| | 112 | |
| | 113 | This static content should be put in the `$TRAC_ENV/htdocs` folder, |
| | 114 | and is accessed by URLs like `<project_URL>/chrome/site/...`. |
| | 115 | |
| | 116 | Example: given a `$TRAC_ENV/htdocs/software-0.1.tar.gz` file, |
| | 117 | the corresponding relative URL would be `/<project_name>/chrome/site/software-0.1.tar.gz`, |
| | 118 | which in turn can be written using the relative link syntax |
| | 119 | in the Wiki: `[/<project_name>/chrome/site/software-0.1.tar.gz]` |
| | 120 | |
| | 121 | The development version of Trac supports a new `htdocs:` TracLinks |
| | 122 | syntax for the above. With this, the example link above can be written simply |
| | 123 | `htdocs:software-0.1.tar.gz`. |
| | 124 | |
