| | 62 | {{{#!div |
| | 63 | Once the service is installed, it might be simpler to run the Registry Editor rather than use the `reg add` command documented above. Navigate to:[[BR]] |
| | 64 | `HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\tracd\Parameters` |
| | 65 | |
| | 66 | Three (string) parameters are provided: |
| | 67 | ||!AppDirectory ||C:\Python26\ || |
| | 68 | ||Application ||python.exe || |
| | 69 | ||!AppParameters ||scripts\tracd-script.py -p 8080 ... || |
| | 70 | |
| | 71 | Note that, if the !AppDirectory is set as above, the paths of the executable ''and'' of the script name and parameter values are relative to the directory. This makes updating Python a little simpler because the change can be limited, here, to a single point. |
| | 72 | (This is true for the path to the .htpasswd file, as well, despite the documentation calling out the /full/path/to/htpasswd; however, you may not wish to store that file under the Python directory.) |
| | 73 | }}} |
| | 74 | |
| | 75 | For Windows 7 User, srvany.exe may not be an option, so you can use [http://www.google.com/search?q=winserv.exe WINSERV] utility and run: |
| | 76 | {{{ |
| | 77 | "C:\path\to\winserv.exe" install tracd -displayname "tracd" -start auto "C:\path\to\python.exe" c:\path\to\python\scripts\tracd-script.py <your tracd parameters>" |
| | 78 | |
| | 79 | net start tracd |
| | 80 | }}} |
| | 81 | |
| | 82 | === Option 2 === |
| | 83 | |
| | 84 | Use [http://trac-hacks.org/wiki/WindowsServiceScript WindowsServiceScript], available at [http://trac-hacks.org/ Trac Hacks]. Installs, removes, starts, stops, etc. your Trac service. |
| | 85 | |
| 62 | | Using tracd with Apache .htpasswd files: |
| 63 | | |
| 64 | | To create a .htpasswd file using htpasswd: |
| 65 | | |
| 66 | | {{{ |
| 67 | | sudo htpasswd -c /path/to/env/.htpasswd username |
| | 88 | Tracd provides support for both Basic and Digest authentication. Digest is considered more secure. The examples below use Digest; to use Basic authentication, replace `--auth` with `--basic-auth` in the command line. |
| | 89 | |
| | 90 | The general format for using authentication is: |
| | 91 | {{{ |
| | 92 | $ tracd -p port --auth="base_project_dir,password_file_path,realm" project_path |
| | 93 | }}} |
| | 94 | where: |
| | 95 | * '''base_project_dir''': the base directory of the project specified as follows: |
| | 96 | * when serving multiple projects: ''relative'' to the `project_path` |
| | 97 | * when serving only a single project (`-s`): the name of the project directory |
| | 98 | Don't use an absolute path here as this won't work. ''Note:'' This parameter is case-sensitive even for environments on Windows. |
| | 99 | * '''password_file_path''': path to the password file |
| | 100 | * '''realm''': the realm name (can be anything) |
| | 101 | * '''project_path''': path of the project |
| | 102 | |
| | 103 | * **`--auth`** in the above means use Digest authentication, replace `--auth` with `--basic-auth` if you want to use Basic auth. Although Basic authentication does not require a "realm", the command parser does, so the second comma is required, followed directly by the closing quote for an empty realm name. |
| | 104 | |
| | 105 | Examples: |
| | 106 | |
| | 107 | {{{ |
| | 108 | $ tracd -p 8080 \ |
| | 109 | --auth="project1,/path/to/passwordfile,mycompany.com" /path/to/project1 |
| | 110 | }}} |
| | 111 | |
| | 112 | Of course, the password file can be be shared so that it is used for more than one project: |
| | 113 | {{{ |
| | 114 | $ tracd -p 8080 \ |
| | 115 | --auth="project1,/path/to/passwordfile,mycompany.com" \ |
| | 116 | --auth="project2,/path/to/passwordfile,mycompany.com" \ |
| | 117 | /path/to/project1 /path/to/project2 |
| | 118 | }}} |
| | 119 | |
| | 120 | Another way to share the password file is to specify "*" for the project name: |
| | 121 | {{{ |
| | 122 | $ tracd -p 8080 \ |
| | 123 | --auth="*,/path/to/users.htdigest,mycompany.com" \ |
| | 124 | /path/to/project1 /path/to/project2 |
| | 125 | }}} |
| | 126 | |
| | 127 | === Basic Authorization: Using a htpasswd password file === |
| | 128 | This section describes how to use `tracd` with Apache .htpasswd files. |
| | 129 | |
| | 130 | To create a .htpasswd file use Apache's `htpasswd` command (see [#GeneratingPasswordsWithoutApache below] for a method to create these files without using Apache): |
| | 131 | {{{ |
| | 132 | $ sudo htpasswd -c /path/to/env/.htpasswd username |
| 71 | | sudo htpasswd /path/to/env/.htpasswd username2 |
| 72 | | }}} |
| 73 | | then for starting the tracd: |
| 74 | | {{{ |
| 75 | | tracd -p 8080 --basic-auth=environmentname,/fullpath/environmentname/.htpasswd,/fullpath/environmentname /fullpath/environmentname |
| 76 | | }}} |
| 77 | | |
| 78 | | |
| 79 | | 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.) |
| 80 | | |
| 81 | | ''Support for Basic authentication was added in version 0.9.'' |
| 82 | | |
| 83 | | The general format for using authentication is: |
| 84 | | |
| 85 | | {{{ |
| 86 | | $ tracd -p port --auth=base_project_dir,password_file_path,realm project_path |
| 87 | | }}} |
| 88 | | |
| 89 | | where: |
| 90 | | |
| 91 | | * '''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 |
| 92 | | * '''password_file_path''' path of the password file |
| 93 | | * '''realm''' realm |
| 94 | | * '''project_path''' path of the project |
| 95 | | |
| 96 | | Example: |
| 97 | | |
| 98 | | {{{ |
| 99 | | $ tracd -p 8080 \ |
| 100 | | --auth=project1,/path/to/users.htdigest,mycompany.com /path/to/project1 |
| 101 | | }}} |
| 102 | | Of course, the digest file can be be shared so that it is used for more than one project: |
| 103 | | {{{ |
| 104 | | $ tracd -p 8080 \ |
| 105 | | --auth=project1,/path/to/users.htdigest,mycompany.com \ |
| 106 | | --auth=project2,/path/to/users.htdigest,mycompany.com \ |
| 107 | | /path/to/project1 /path/to/project2 |
| 108 | | }}} |
| 109 | | |
| 110 | | Another way to share the digest file is to specify "*" |
| 111 | | for the project name: |
| 112 | | {{{ |
| 113 | | $ tracd -p 8080 \ |
| 114 | | --auth="*",/path/to/users.htdigest,mycompany.com \ |
| 115 | | /path/to/project1 /path/to/project2 |
| 116 | | }}} |
| 117 | | If using the `-s` parameter for serving a Trac environment from the root of a domain, one must use `*` for the project name |
| 118 | | |
| 119 | | == How to set up an htdigest password file == |
| | 136 | $ sudo htpasswd /path/to/env/.htpasswd username2 |
| | 137 | }}} |
| | 138 | |
| | 139 | Then to start `tracd` run something like this: |
| | 140 | {{{ |
| | 141 | $ tracd -p 8080 --basic-auth="projectdirname,/fullpath/environmentname/.htpasswd,realmname" /fullpath/environmentname |
| | 142 | }}} |
| | 143 | |
| | 144 | For example: |
| | 145 | {{{ |
| | 146 | $ tracd -p 8080 --basic-auth="testenv,/srv/tracenv/testenv/.htpasswd,My Test Env" /srv/tracenv/testenv |
| | 147 | }}} |
| | 148 | ''Note:'' You might need to pass "-m" as a parameter to htpasswd on some platforms (OpenBSD). |
| | 149 | |
| | 150 | === Digest authentication: Using a htdigest password file === |
| 161 | | 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): |
| 162 | | |
| 163 | | {{{ |
| 164 | | python trac-digest.py -u username -p password >> c:\digest.txt |
| 165 | | tracd --port 8000 --auth=proj_name,c:\digest.txt,trac c:\path\to\proj_name |
| 166 | | }}} |
| 167 | | |
| 168 | | 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.) |
| 169 | | |
| 170 | | It is possible to use md5sum utility to generate digest-password file using such method: |
| | 194 | Note: If you use the above script you must set the realm in the `--auth` argument to '''`trac`'''. Example usage (assuming you saved the script as trac-digest.py): |
| | 195 | |
| | 196 | {{{ |
| | 197 | $ python trac-digest.py -u username -p password >> c:\digest.txt |
| | 198 | $ tracd --port 8000 --auth=proj_name,c:\digest.txt,trac c:\path\to\proj_name |
| | 199 | }}} |
| | 200 | |
| | 201 | ==== Using `md5sum` |
| | 202 | It is possible to use `md5sum` utility to generate digest-password file: |
| | 208 | == Reference == |
| | 209 | |
| | 210 | Here's the online help, as a reminder (`tracd --help`): |
| | 211 | {{{ |
| | 212 | Usage: tracd [options] [projenv] ... |
| | 213 | |
| | 214 | Options: |
| | 215 | --version show program's version number and exit |
| | 216 | -h, --help show this help message and exit |
| | 217 | -a DIGESTAUTH, --auth=DIGESTAUTH |
| | 218 | [projectdir],[htdigest_file],[realm] |
| | 219 | --basic-auth=BASICAUTH |
| | 220 | [projectdir],[htpasswd_file],[realm] |
| | 221 | -p PORT, --port=PORT the port number to bind to |
| | 222 | -b HOSTNAME, --hostname=HOSTNAME |
| | 223 | the host name or IP address to bind to |
| | 224 | --protocol=PROTOCOL http|scgi|ajp |
| | 225 | -q, --unquote unquote PATH_INFO (may be needed when using ajp) |
| | 226 | --http10 use HTTP/1.0 protocol version (default) |
| | 227 | --http11 use HTTP/1.1 protocol version instead of HTTP/1.0 |
| | 228 | -e PARENTDIR, --env-parent-dir=PARENTDIR |
| | 229 | parent directory of the project environments |
| | 230 | --base-path=BASE_PATH |
| | 231 | the initial portion of the request URL's "path" |
| | 232 | -r, --auto-reload restart automatically when sources are modified |
| | 233 | -s, --single-env only serve a single project without the project list |
| | 234 | }}} |
| | 235 | |
| 189 | | which in turn can be written using the relative link syntax |
| 190 | | in the Wiki: `[/<project_name>/chrome/site/software-0.1.tar.gz]` |
| 191 | | |
| 192 | | The development version of Trac supports a new `htdocs:` TracLinks |
| 193 | | syntax for the above. With this, the example link above can be written simply |
| 194 | | `htdocs:software-0.1.tar.gz`. |
| 195 | | |
| 196 | | === Using apache rewrite rules === |
| 197 | | 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. |
| | 249 | which in turn can be written as `htdocs:software-0.1.tar.gz` (TracLinks syntax) or `[/<project_name>/chrome/site/software-0.1.tar.gz]` (relative link syntax). |
| | 250 | |
| | 251 | ''Support for `htdocs:` TracLinks syntax was added in version 0.10'' |
| | 252 | |
| | 253 | === Using tracd behind a proxy |
| | 254 | |
| | 255 | In some situations when you choose to use tracd behind Apache or another web server. |
| | 256 | |
| | 257 | In this situation, 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. |
| | 258 | |
| | 259 | If you're using the AJP protocol to connect with `tracd` (which is possible if you have flup installed), then you might experience problems with double quoting. Consider adding the `--unquote` parameter. |
| | 260 | |
| | 261 | See also [trac:TracOnWindowsIisAjp], [trac:TracNginxRecipe]. |