Changes between Version 2 and Version 3 of TracStandalone


Ignore:
Timestamp:
Aug 5, 2014, 3:58:25 PM (10 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracStandalone

    v2 v3  
    6060The spacing here is important.
    6161
     62{{{#!div
     63Once 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
     66Three (string) parameters are provided:
     67||!AppDirectory ||C:\Python26\ ||
     68||Application ||python.exe ||
     69||!AppParameters ||scripts\tracd-script.py -p 8080 ... ||
     70
     71Note 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
    6275For 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:
    6376{{{
     
    7184Use [http://trac-hacks.org/wiki/WindowsServiceScript WindowsServiceScript], available at [http://trac-hacks.org/ Trac Hacks]. Installs, removes, starts, stops, etc. your Trac service.
    7285
     86=== Option 3 ===
     87
     88also cygwin's cygrunsrv.exe can be used:
     89{{{
     90$ cygrunsrv --install tracd --path /cygdrive/c/Python27/Scripts/tracd.exe --args '--port 8000 --env-parent-dir E:\IssueTrackers\Trac\Projects'
     91$ net start tracd
     92}}}
     93
    7394== Using Authentication ==
    7495
    75 Using tracd with Apache .htpasswd files:
    76 
    77 To create a .htpasswd file using htpasswd:
    78 
    79 {{{
    80  $ htpasswd -c /path/to/env/.htpasswd username
    81 }}}
    82 then for additional users:
    83 {{{
    84  $ htpasswd /path/to/env/.htpasswd username2
    85 }}}
    86 then for starting the tracd (on windows skip the "=" after --basic-auth):
    87 {{{
    88 tracd -p 8080 --basic-auth=environmentname,/fullpath/environmentname/.htpasswd,/fullpath/environmentname /fullpath/environmentname
    89 }}}
    90 
    91  `environmentname` is the directory name of the Trac project folder, as opposed to `/fullpath/environmentname` which is the full path to the Trac project folder. See below for another example.
    92 
    93 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.)
    94 
    95   ''Support for Basic authentication was added in version 0.9.''
    96 
    97 The general format for using authentication is (replace `--auth` with `--basic-auth` if you want to use Basic auth):
    98 
     96Tracd allows you to run Trac without the need for Apache, but you can take advantage of Apache's password tools (htpasswd and htdigest) to easily create a password file in the proper format for tracd to use in authentication. (It is also possible to create the password file without htpasswd or htdigest; see below for alternatives)
     97
     98Tracd 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.
     99
     100The general format for using authentication is:
    99101{{{
    100102 $ tracd -p port --auth="base_project_dir,password_file_path,realm" project_path
    101103}}}
    102 
    103104where:
    104 
    105105 * '''base_project_dir''': the base directory of the project specified as follows:
    106106   * when serving multiple projects: ''relative'' to the `project_path`
     
    111111 * '''project_path''': path of the project
    112112
     113 * **`--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.
     114
    113115Examples:
    114116
     
    133135}}}
    134136
    135 === Using a htpasswd password file ===
     137=== Basic Authorization: Using a htpasswd password file ===
    136138This section describes how to use `tracd` with Apache .htpasswd files.
    137139
     140  Note: It is necessary (at least with Python 2.6) to install the fcrypt package in order to
     141  decode some htpasswd formats.  Trac source code attempt an `import crypt` first, but there
     142  is no such package for Python 2.6. Only `SHA-1` passwords (since Trac 1.0) work without this module.
     143
    138144To create a .htpasswd file use Apache's `htpasswd` command (see [#GeneratingPasswordsWithoutApache below] for a method to create these files without using Apache):
    139 
    140145{{{
    141146 $ sudo htpasswd -c /path/to/env/.htpasswd username
     
    147152
    148153Then to start `tracd` run something like this:
    149 
    150154{{{
    151155 $ tracd -p 8080 --basic-auth="projectdirname,/fullpath/environmentname/.htpasswd,realmname" /fullpath/environmentname
     
    153157
    154158For example:
    155 
    156159{{{
    157160 $ tracd -p 8080 --basic-auth="testenv,/srv/tracenv/testenv/.htpasswd,My Test Env" /srv/tracenv/testenv
    158161}}}
    159 
    160162''Note:'' You might need to pass "-m" as a parameter to htpasswd on some platforms (OpenBSD).
    161163
    162 === Using a htdigest password file ===
     164=== Digest authentication: Using a htdigest password file ===
    163165
    164166If 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.
    165167
    166 Note that you can start tracd without the --auth argument, but if you click on the ''Login'' link you will get an error.
     168Note that you can start tracd without the `--auth` argument, but if you click on the ''Login'' link you will get an error.
    167169
    168170=== Generating Passwords Without Apache ===
    169171
    170 If you don't have Apache available, you can use this simple Python script to generate your passwords:
     172Basic Authorization can be accomplished via this [http://aspirine.org/htpasswd_en.html online HTTP Password generator] which also supports `SHA-1`.  Copy the generated password-hash line to the .htpasswd file on your system. Note that Windows Python lacks the "crypt" module that is the default hash type for htpasswd ; Windows Python can grok MD5 password hashes just fine and you should use MD5.
     173
     174You can use this simple Python script to generate a '''digest''' password file:
    171175
    172176{{{
     
    202206}}}
    203207
    204 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):
     208Note: 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):
    205209
    206210{{{
     
    209213}}}
    210214
    211 
    212 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). Make sure to use -m option for it.  If you do not have Apache, [trac:source:/tags/trac-0.11/contrib/htpasswd.py htpasswd.py] may help.  (Note that it requires a `crypt` or `fcrypt` module; see the source comments for details.)
    213 
    214 It is possible to use md5sum utility to generate digest-password file using such method:
    215 {{{
    216  $ printf "${user}:trac:${password}" | md5sum - >>user.htdigest
    217 }}}
    218 and manually delete " -" from the end and add "${user}:trac:" to the start of line from 'to-file'.
     215==== Using `md5sum`
     216It is possible to use `md5sum` utility to generate digest-password file:
     217{{{
     218user=
     219realm=
     220password=
     221path_to_file=
     222echo ${user}:${realm}:$(printf "${user}:${realm}:${password}" | md5sum - | sed -e 's/\s\+-//') > ${path_to_file}
     223}}}
     224
     225== Reference ==
     226
     227Here's the online help, as a reminder (`tracd --help`):
     228{{{
     229Usage: tracd [options] [projenv] ...
     230
     231Options:
     232  --version             show program's version number and exit
     233  -h, --help            show this help message and exit
     234  -a DIGESTAUTH, --auth=DIGESTAUTH
     235                        [projectdir],[htdigest_file],[realm]
     236  --basic-auth=BASICAUTH
     237                        [projectdir],[htpasswd_file],[realm]
     238  -p PORT, --port=PORT  the port number to bind to
     239  -b HOSTNAME, --hostname=HOSTNAME
     240                        the host name or IP address to bind to
     241  --protocol=PROTOCOL   http|scgi|ajp|fcgi
     242  -q, --unquote         unquote PATH_INFO (may be needed when using ajp)
     243  --http10              use HTTP/1.0 protocol version instead of HTTP/1.1
     244  --http11              use HTTP/1.1 protocol version (default)
     245  -e PARENTDIR, --env-parent-dir=PARENTDIR
     246                        parent directory of the project environments
     247  --base-path=BASE_PATH
     248                        the initial portion of the request URL's "path"
     249  -r, --auto-reload     restart automatically when sources are modified
     250  -s, --single-env      only serve a single project without the project list
     251  -d, --daemonize       run in the background as a daemon
     252  --pidfile=PIDFILE     when daemonizing, file to which to write pid
     253  --umask=MASK          when daemonizing, file mode creation mask to use, in
     254                        octal notation (default 022)
     255  --group=GROUP         the group to run as
     256  --user=USER           the user to run as
     257}}}
     258
     259Use the -d option so that tracd doesn't hang if you close the terminal window where tracd was started.
    219260
    220261== Tips ==
     
    235276 ''Support for `htdocs:` TracLinks syntax was added in version 0.10''
    236277
    237 === Using apache rewrite rules ===
    238 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.
     278=== Using tracd behind a proxy
     279
     280In some situations when you choose to use tracd behind Apache or another web server.
     281
     282In 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.
     283
     284If 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.
     285
     286See also [trac:TracOnWindowsIisAjp], [trac:TracNginxRecipe].
     287
     288=== Authentication for tracd behind a proxy
     289It is convenient to provide central external authentication to your tracd instances, instead of using {{{--basic-auth}}}. There is some discussion about this in #9206.
     290
     291Below is example configuration based on Apache 2.2, mod_proxy, mod_authnz_ldap.
     292
     293First we bring tracd into Apache's location namespace.
     294
     295{{{
     296<Location /project/proxified>
     297        Require ldap-group cn=somegroup, ou=Groups,dc=domain.com
     298        Require ldap-user somespecificusertoo
     299        ProxyPass http://localhost:8101/project/proxified/
     300        # Turns out we don't really need complicated RewriteRules here at all
     301        RequestHeader set REMOTE_USER %{REMOTE_USER}s
     302</Location>
     303}}}
     304
     305Then we need a single file plugin to recognize HTTP_REMOTE_USER header as valid authentication source. HTTP headers like '''HTTP_FOO_BAR''' will get converted to '''Foo-Bar''' during processing. Name it something like '''remote-user-auth.py''' and drop it into '''proxified/plugins''' directory:
     306{{{
     307#!python
     308from trac.core import *
     309from trac.config import BoolOption
     310from trac.web.api import IAuthenticator
     311
     312class MyRemoteUserAuthenticator(Component):
     313
     314    implements(IAuthenticator)
     315
     316    obey_remote_user_header = BoolOption('trac', 'obey_remote_user_header', 'false',
     317               """Whether the 'Remote-User:' HTTP header is to be trusted for user logins
     318                (''since ??.??').""")
     319
     320    def authenticate(self, req):
     321        if self.obey_remote_user_header and req.get_header('Remote-User'):
     322            return req.get_header('Remote-User')
     323        return None
     324
     325}}}
     326
     327Add this new parameter to your TracIni:
     328{{{
     329...
     330[trac]
     331...
     332obey_remote_user_header = true
     333...
     334}}}
     335
     336Run tracd:
     337{{{
     338tracd -p 8101 -r -s proxified --base-path=/project/proxified
     339}}}
     340
     341Note that if you want to install this plugin for all projects, you have to put it in your [TracPlugins#Plugindiscovery global plugins_dir] and enable it in your global trac.ini.
     342
     343Global config (e.g. `/srv/trac/conf/trac.ini`):
     344{{{
     345[components]
     346remote-user-auth.* = enabled
     347[inherit]
     348plugins_dir = /srv/trac/plugins
     349[trac]
     350obey_remote_user_header = true
     351}}}
     352
     353Environment config (e.g. `/srv/trac/envs/myenv`):
     354{{{
     355[inherit]
     356file = /srv/trac/conf/trac.ini
     357}}}
    239358
    240359=== Serving a different base path than / ===
     
    245364
    246365----
    247 See also: TracInstall, TracCgi, TracModPython, TracGuide, [trac:TracOnWindowsStandalone?version=13#RunningTracdasservice Running tracd.exe as a Windows service], [trac:TracOnWindowsIisAjp], [trac:TracNginxRecipe]
     366See also: TracInstall, TracCgi, TracModPython, TracGuide, [trac:TracOnWindowsStandalone#RunningTracdasservice Running tracd.exe as a Windows service]