| 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. |
| | 32 | 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 |
| | 33 | different projects unique. So if you use `/project1/path/to` and `/project2/path/to`, you will only see the second project. |
| | 34 | |
| | 35 | 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: |
| | 36 | {{{ |
| | 37 | $ tracd -p 8080 -e /path/to |
| | 38 | }}} |
| | 39 | |
| | 40 | To exit the server on Windows, be sure to use {{{CTRL-BREAK}}} -- using {{{CTRL-C}}} will leave a Python process running in the background. |
| | 41 | |
| | 42 | When running as a Windows service using a utility such as [http://www.google.com/search?q=srvany.exe SRVANY], stopping or restarting the service will also leave a Python process running -- restart the system instead. |
| | 43 | |
| | 63 | |
| | 64 | 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. (You must still specify a dialogic "realm", which can be an empty string by trailing the BASICAUTH with a comma.) |
| | 65 | |
| | 66 | ''Support for Basic authentication was added in version 0.9.'' |
| | 67 | |
| | 68 | The general format for using authentication is: |
| | 69 | |
| | 70 | {{{ |
| | 71 | $ tracd -p port --auth=base_project_dir,password_file_path,realm project_path |
| | 72 | }}} |
| | 73 | |
| | 74 | where: |
| | 75 | |
| | 76 | * '''base_project_dir''' is the base directory of the project; note: this doesn't refer to the project name, and it is case-sensitive even for windows environments |
| | 77 | * '''password_file_path''' path of the password file |
| | 78 | * '''realm''' realm |
| | 79 | * '''project_path''' path of the project |
| | 80 | |
| | 81 | Example: |
| | 82 | |
| | 83 | {{{ |
| | 84 | $ tracd -p 8080 \ |
| | 85 | --auth=project1,/path/to/users.htdigest,mycompany.com /path/to/project1 |
| | 86 | }}} |
| | 94 | |
| | 95 | Another way to share the digest file is to specify "*" |
| | 96 | for the project name: |
| | 97 | {{{ |
| | 98 | $ tracd -p 8080 \ |
| | 99 | --auth="*",/path/to/users.htdigest,mycompany.com \ |
| | 100 | /path/to/project1 /path/to/project2 |
| | 101 | }}} |
| | 102 | If using the `-s` parameter for serving a Trac environment from the root of a domain, one must use `*` for the project name |
| | 103 | |
| | 104 | == How to set up an htdigest password file == |
| | 105 | |
| | 106 | 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. |
| | 107 | |
| | 108 | Note that you can start tracd without the --auth argument, but if you click on the ''Login'' link you will get an error. |
| | 146 | 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): |
| | 147 | |
| | 148 | {{{ |
| | 149 | python trac-digest.py -u username -p password >> c:\digest.txt |
| | 150 | tracd --port 8000 --auth=proj_name,c:\digest.txt,trac c:\path\to\proj_name |
| | 151 | }}} |
| | 152 | |
| | 153 | Note: If you would like to use --basic-auth you need to use htpasswd tool from apache server to generate .htpasswd file. The remaining part is similar but make sure to use empty realm (i.e. coma after path). When using on Windows make sure to use -m option for it (did not tested it on *nix, so not sure if that is the case there). If you do not have Apache, [trac:source:/tags/trac-0.11b2/contrib/htpasswd.py htpasswd.py] may help. (Note that it requires a `crypt` or `fcrypt` module; see the source comments for details.) |
| | 154 | |
| | 155 | It is possible to use md5sum utility to generate digest-password file using such method: |
| | 156 | {{{ |
| | 157 | echo -e "${user}:trac:${password}\c" | md5sum - >>to-file |
| | 158 | }}} |
| | 159 | and manually delete " -" from the end and add "${user}:trac:" to the start of line from 'to-file'. You can see attachment:trac-digest-corrected.sh for detail. |
| | 160 | |
| | 161 | == Tips == |
| | 162 | |
| | 163 | === Serving static content === |
| | 164 | |
| | 165 | If `tracd` is the only webserver used for the project, |
| | 166 | it can also be used to distribute static content |
| | 167 | (tarballs, Doxygen documentation, etc.) |
| | 168 | |
| | 169 | This static content should be put in the `$TRAC_ENV/htdocs` folder, |
| | 170 | and is accessed by URLs like `<project_URL>/chrome/site/...`. |
| | 171 | |
| | 172 | Example: given a `$TRAC_ENV/htdocs/software-0.1.tar.gz` file, |
| | 173 | the corresponding relative URL would be `/<project_name>/chrome/site/software-0.1.tar.gz`, |
| | 174 | which in turn can be written using the relative link syntax |
| | 175 | in the Wiki: `[/<project_name>/chrome/site/software-0.1.tar.gz]` |
| | 176 | |
| | 177 | The development version of Trac supports a new `htdocs:` TracLinks |
| | 178 | syntax for the above. With this, the example link above can be written simply |
| | 179 | `htdocs:software-0.1.tar.gz`. |
| | 180 | |
| | 181 | === Using apache rewrite rules === |
| | 182 | In some situations when you choose to use tracd behind apache, you might experience issues with redirects, like being redirected to URLs with the wrong host or protocol. In this case (and only in this case), setting the `[trac] use_base_url_for_redirect` to `true` can help, as this will force Trac to use the value of `[trac] base_url` for doing the redirects. |
| | 183 | |
| | 184 | === Serving a different base path than / === |
| | 185 | Tracd supports serving projects with different base urls than /<project>. The parameter name to change this is |
| | 186 | {{{ |
| | 187 | tracd --base-path=/some/path |
| | 188 | }}} |
| | 189 | |
