Changes between Version 2 and Version 3 of TracStandalone

Jan 25, 2009 10:55:12 AM (11 years ago)



  • TracStandalone

    v2 v3  
    11= Tracd = 
    3 Tracd is a lightweight stand-alone Trac server. In most cases it's easier to setup and runs faster than trac.cgi. 
     3Tracd is a lightweight standalone Trac web server. In most cases it's easier to setup and runs faster than the [wiki:TracCgi CGI script]. 
    65== Pros == 
    87 * Fewer dependencies: You don't need to install apache or any other web-server. 
    9  * Fast: Should be as fast as the TracModPython version (much faster than the 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). 
    1111== Cons == 
    13  * Less features: Tracd implements a very simple web-server and is not as configurable as apache. 
    14  * Only htdigest authentication: Tracd can currently only authenticate users against apache-htdigest files. 
    15  * No native https support: [ sslwrap] can be used instead, 
    16    or [ STUNNEL]. 
     13 * Fewer features: Tracd implements a very simple web-server and is not as configurable or as scalable as Apache HTTPD. 
     14 * No native HTTPS support: [ sslwrap] can be used instead, 
     15   or [ stunnel -- a tutorial on how to use stunnel with tracd] or Apache with mod_proxy. 
    1817== Usage examples == 
    2221 $ tracd -p 8080 /path/to/project 
     23Stricly speaking this will make your Trac accessible to everybody from your network rather than ''localhost only''. To truly limit it use ''--hostname'' option. 
     25 $ tracd --hostname=localhost -p 8080 /path/to/project 
    2427With more than one project. (http://localhost:8080/project1/ and http://localhost:8080/project2/) 
    2629 $ tracd -p 8080 /path/to/project1 /path/to/project2 
    28 With htdigest authentication. The file /tmp/users.htdigest contain user accounts for project1 with the realm "". 
     32You can't have the last portion of the path identical between the projects since Trac uses that name to keep the URLs of the 
     33different projects unique. So if you use `/project1/path/to` and `/project2/path/to`, you will only see the second project. 
     35An 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: 
    30  $ tracd -p 8080 --auth project1,/tmp/users.htdigest, /path/to/project1 
     37 $ tracd -p 8080 -e /path/to 
    32 htdigest authentication can also be used for more than one project. 
    33 The digest file can be shared: 
     40To exit the server on Windows, be sure to use {{{CTRL-BREAK}}} -- using {{{CTRL-C}}} will leave a Python process running in the background. 
     43== Using Authentication == 
     45Using tracd with Apache .htpasswd files: 
     47To create a .htpasswd file using htpasswd: 
     50sudo htpasswd -c /path/to/env/.htpasswd username 
     52then for additional users: 
     54sudo htpasswd /var/www/html/.htpasswd-users username2 
     56then for starting the tracd: 
     58tracd -p 8080 --basic-auth=environmentname,/fullpath/environmentname/.htpasswd,/fullpath/environmentname /fullpath/environmentname 
     62Tracd 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.) 
     64  ''Support for Basic authentication was added in version 0.9.'' 
     66The general format for using authentication is: 
     69 $ tracd -p port --auth=base_project_dir,password_file_path,realm project_path 
     74 * '''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 
     75 * '''password_file_path''' path of the password file 
     76 * '''realm''' realm 
     77 * '''project_path''' path of the project 
    3582 $ tracd -p 8080 \ 
    36    --auth project1,/tmp/users.htdigest, \ 
    37    --auth project2,/tmp/users.htdigest, \ 
     83   --auth=project1,/path/to/users.htdigest, /path/to/project1 
     85Of course, the digest file can be be shared so that it is used for more than one project: 
     87 $ tracd -p 8080 \ 
     88   --auth=project1,/path/to/users.htdigest, \ 
     89   --auth=project2,/path/to/users.htdigest, \ 
    3890   /path/to/project1 /path/to/project2 
    41 == Tracd on Windows == 
    43 tracd also works on Windows.  
    44 But on that platform, the sensitivity on multithreading issues is high, 
    45 and you ''might'' have problems (i.e. crashes of the Python interpreter). 
    46 If this happens, you can force tracd to operate in single-threaded mode: 
     93Another way to share the digest file is to specify "*" 
     94for the project name: 
    48 #!text/x-diff 
    49 Index: trac/web/ 
    50 =================================================================== 
    51 --- trac/web/      (revision 1862) 
    52 +++ trac/web/      (working copy) 
    53 @@ -124,7 +124,7 @@ 
    54          return auth['username'] 
    57 -class TracHTTPServer(ThreadingMixIn, HTTPServer): 
    58 +class TracHTTPServer(HTTPServer): 
    60      projects = None 
     96 $ tracd -p 8080 \ 
     97   --auth=*,/path/to/users.htdigest, \ 
     98   /path/to/project1 /path/to/project2 
    63 Please also report any such issue, as they are believed to be fixed by now. 
     101== How to set up an htdigest password file == 
     103If you have Apache available, you can use the htdigest command to generate the password file. Type 'htdigest' to get some usage instructions, or read [ 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. 
    66 == Generating passwords on Windows == 
     105Note that you can start tracd without the --auth argument, but if you click on the ''Login'' link you will get an error. 
    68 If you don't have Apache available, you can use this Python script to generate your passwords (code borrowed heavily from #845): 
     107== Generating Passwords Without Apache == 
     109If you don't have Apache available, you can use this simple Python script to generate your passwords: 
    71113from optparse import OptionParser 
    72114import md5 
     135Note: 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 
     138python -u username -p password >> c:\digest.txt 
     139tracd --port 8000 --auth=proj_name,c:\digest.txt,trac c:\path\to\proj_name 
     142Note: 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/] may help.  (Note that it requires a `crypt` or `fcrypt` module; see the source comments for details.) 
     144It is possible to use md5sum utility to generate digest-password file using such method: 
     146echo -e "${user}:trac:${password}\c" | md5sum - >>to-file 
     148and manually delete " -" from the end and add "${user}:trac:" to the start of line from 'to-file'. You can see for detail. 
     150== Tips == 
     152=== Serving static content === 
     154If `tracd` is the only webserver used for the project,  
     155it can also be used to distribute static content  
     156(tarballs, Doxygen documentation, etc.) 
     158This static content should be put in the `$TRAC_ENV/htdocs` folder, 
     159and is accessed by URLs like `<project_URL>/chrome/site/...`. 
     161Example: given a `$TRAC_ENV/htdocs/software-0.1.tar.gz` file, 
     162the corresponding relative URL would be `/<project_name>/chrome/site/software-0.1.tar.gz`,  
     163which in turn can be written using the relative link syntax 
     164in the Wiki: `[/<project_name>/chrome/site/software-0.1.tar.gz]`  
     166The development version of Trac supports a new `htdocs:` TracLinks  
     167syntax for the above. With this, the example link above can be written simply  
     170=== Using apache rewrite rules === 
     171In 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. 
     173=== Serving a different base path than / === 
     174Tracd supports serving projects with different base urls then /<project>. The parameter name to change this is 
     176tracd --base-path=/some/path 
    94 See also: [source:trunk/README.tracd#latest README.tracd], TracGuide, TracInstall, TracModPython 
     180See also: TracInstall, TracCgi, TracModPython, TracGuide