# Changes between Version 1 and Version 2 of TracStandalone

Show
Ignore:
Timestamp:
07/11/08 17:40:33 (6 years ago)
Comment:

--

Unmodified
Removed
Modified
• ## TracStandalone

v1 v2
66
77 * Fewer dependencies: You don't need to install apache or any other web-server.
8  * Fast: Should be as fast as the [wiki:TracModPython mod_python] version (and much faster than the [wiki:TracCgi CGI]).
8 * Fast: Should be almost as fast as the [wiki:TracModPython mod_python] version (and much faster than the [wiki:TracCgi CGI]).
9 * Automatic reloading: For development, Tracd can be used in ''auto_reload'' mode, which will automatically restart the server whenever you make a change to the code (in Trac itself or in a plugin).
910
1011== Cons ==
1112
12  * Less features: Tracd implements a very simple web-server and is not as configurable as Apache HTTPD.
13 * Fewer features: Tracd implements a very simple web-server and is not as configurable or as scalable as Apache HTTPD.
1314 * No native HTTPS support: [http://www.rickk.com/sslwrap/ sslwrap] can be used instead,
14    or [http://lists.edgewall.com/archive/trac/2005-August/004381.html STUNNEL]
15   or [http://trac.edgewall.org/wiki/STunnelTracd stunnel -- a tutorial on how to use stunnel with tracd] or Apache with mod_proxy
1516
1617== Usage examples ==
2526}}}
2627
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.
28You can't have the last portion of the path identical between the projects since Trac uses that name to keep the URLs of the
29different projects unique. So if you use /project1/path/to and /project2/path/to, you will only see the second project.
30
31An 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}}} 2935 3036== Using Authentication == 3238Tracd 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. 3339 34 If the file /path/to/users.htdigest contain user accounts for project1 with the realm "mycompany.com", you'd use the following command-line to start tracd: 40 ''Support for Basic authentication was added in version 0.9.'' 41 42If 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: 3543{{{ 3644$ tracd -p 8080 --auth project1,/path/to/users.htdigest,mycompany.com /path/to/project1
3745}}}
38 ''Note that the project “name” passed to the --auth option is actually the base name of the project environment directory.""
46
47'''Note''': the project "name" passed to the --auth option is the base name of the project environment directory.
3948
4049Of course, the digest file can be be shared so that it is used for more than one project:
4554   /path/to/project1 /path/to/project2
4655}}}
56
57Another way to share the digest file is to specify "*"
58for 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 67If 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 69Note that you can start tracd without the --auth argument, but if you click on the ''Login'' link you will get an error. 4770 4871== Generating Passwords Without Apache == 7396}}} 7497 98Note: 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{{{ 101python trac-digest.py -u username -p password >> c:\digest.txt 102python 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 109If tracd is the only webserver used for the project, 110it can also be used to distribute static content 111(tarballs, Doxygen documentation, etc.) 112 113This static content should be put in the $TRAC_ENV/htdocs folder,
114and is accessed by URLs like <project_URL>/chrome/site/....
115
116Example: given a \$TRAC_ENV/htdocs/software-0.1.tar.gz file,
117the corresponding relative URL would be /<project_name>/chrome/site/software-0.1.tar.gz,
118which in turn can be written using the relative link syntax
119in the Wiki: [/<project_name>/chrome/site/software-0.1.tar.gz]
120
121The development version of Trac supports a new htdocs: TracLinks
122syntax for the above. With this, the example link above can be written simply
123htdocs:software-0.1.tar.gz.
124
75125----