# Changes between Version 3 and Version 4 of TracStandalone

Ignore:
Timestamp:
04/02/08 19:22:37 (5 years ago)
Comment:

--

### Legend:

Unmodified
 v3 $tracd -p 8080 /path/to/project }}} Stricly speaking this will make your Trac accessible to everybody from your network rather than ''localhost only''. To truly limit it use ''--hostname'' option. {{{$ tracd --hostname=localhost -p 8080 /path/to/project }}} With more than one project. (http://localhost:8080/project1/ and http://localhost:8080/project2/) {{{ }}} To exit the server on Windows, be sure to use {{{CTRL-BREAK}}} -- using {{{CTRL-C}}} will leave a Python process running in the background. == 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. 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.) ''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: The general format for using authentication is: {{{ $tracd -p 8080 --auth project1,/path/to/users.htdigest,mycompany.com /path/to/project1$ tracd -p port --auth=base_project_dir,password_file_path,realm project_path }}} '''Note''': the project "name" passed to the --auth option is the base name of the project environment directory. where: * '''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 * '''password_file_path''' path of the password file * '''realm''' realm * '''project_path''' path of the project Example: {{{ $tracd -p 8080 \ --auth=project1,/path/to/users.htdigest,mycompany.com /path/to/project1 }}} Of course, the digest file can be be shared so that it is used for more than one project: {{{$ tracd -p 8080 \ --auth project1,/path/to/users.htdigest,mycompany.com \ --auth project2,/path/to/users.htdigest,mycompany.com \ --auth=project1,/path/to/users.htdigest,mycompany.com \ --auth=project2,/path/to/users.htdigest,mycompany.com \ /path/to/project1 /path/to/project2 }}} {{{ \$ tracd -p 8080 \ --auth *,/path/to/users.htdigest,mycompany.com \ --auth=*,/path/to/users.htdigest,mycompany.com \ /path/to/project1 /path/to/project2 }}} {{{ #!python from optparse import OptionParser import md5 {{{ python trac-digest.py -u username -p password >> c:\digest.txt python tracd --port 8000 --auth proj_name,c:\digest.txt,trac c:\path\to\proj_name tracd --port 8000 --auth=proj_name,c:\digest.txt,trac c:\path\to\proj_name }}} 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). == Tips == htdocs:software-0.1.tar.gz. === Using apache rewrite rules === 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. === Serving a different base path than / === Tracd supports serving projects with different base urls then /. The parameter name to change this is {{{ tracd --base-path=/some/path }}} ---- See also: TracInstall, TracCgi, TracModPython, TracGuide ---- '''Translation:''' * [https://opensvn.csie.org/traccgi/trac_rus/wiki/StandAloneTracForTeapot Russian] (перевод на Русский)