Changes between Version 1 and Version 2 of TracStandalone
- Timestamp:
- Dec 15, 2008, 9:52:20 AM (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracStandalone
v1 v2 21 21 $ tracd -p 8080 /path/to/project 22 22 }}} 23 Stricly speaking this will make your Trac accessible to everybody from your network rather than ''localhost only''. To truly limit it use ''--hostname'' option. 24 {{{ 25 $ tracd --hostname=localhost -p 8080 /path/to/project 26 }}} 23 27 With more than one project. (http://localhost:8080/project1/ and http://localhost:8080/project2/) 24 28 {{{ … … 34 38 }}} 35 39 40 To exit the server on Windows, be sure to use {{{CTRL-BREAK}}} -- using {{{CTRL-C}}} will leave a Python process running in the background. 41 42 When running as a Windows service using a utility such as [http://www.google.com/search?q=srvany.exe SRVANY], stopping or restarting the service will also leave a Python process running -- restart the system instead. 43 44 36 45 == Using Authentication == 37 46 38 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. 47 Using tracd with Apache .htpasswd files: 48 49 To create a .htpasswd file using htpasswd: 50 51 {{{ 52 sudo htpasswd -c /path/to/env/.htpasswd username 53 }}} 54 then for additional users: 55 {{{ 56 sudo htpasswd /path/to/env/.htpasswd username2 57 }}} 58 then for starting the tracd: 59 {{{ 60 tracd -p 8080 --basic-auth=environmentname,/fullpath/environmentname/.htpasswd,/fullpath/environmentname /fullpath/environmentname 61 }}} 62 63 64 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.) 39 65 40 66 ''Support for Basic authentication was added in version 0.9.'' 41 67 42 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: 68 The general format for using authentication is: 69 43 70 {{{ 44 $ tracd -p 8080 --auth project1,/path/to/users.htdigest,mycompany.com /path/to/project171 $ tracd -p port --auth=base_project_dir,password_file_path,realm project_path 45 72 }}} 46 73 47 '''Note''': the project "name" passed to the `--auth` option is the base name of the project environment directory. 74 where: 48 75 76 * '''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 77 * '''password_file_path''' path of the password file 78 * '''realm''' realm 79 * '''project_path''' path of the project 80 81 Example: 82 83 {{{ 84 $ tracd -p 8080 \ 85 --auth=project1,/path/to/users.htdigest,mycompany.com /path/to/project1 86 }}} 49 87 Of course, the digest file can be be shared so that it is used for more than one project: 50 88 {{{ 51 89 $ tracd -p 8080 \ 52 --auth 53 --auth 90 --auth=project1,/path/to/users.htdigest,mycompany.com \ 91 --auth=project2,/path/to/users.htdigest,mycompany.com \ 54 92 /path/to/project1 /path/to/project2 55 93 }}} … … 59 97 {{{ 60 98 $ tracd -p 8080 \ 61 --auth *,/path/to/users.htdigest,mycompany.com \99 --auth="*",/path/to/users.htdigest,mycompany.com \ 62 100 /path/to/project1 /path/to/project2 63 101 }}} 102 If using the `-s` parameter for serving a Trac environment from the root of a domain, one must use `*` for the project name 64 103 65 104 == How to set up an htdigest password file == … … 74 113 75 114 {{{ 115 #!python 76 116 from optparse import OptionParser 77 import md5 117 # The md5 module is deprecated in Python 2.5 118 try: 119 from hashlib import md5 120 except ImportError: 121 from md5 import md5 122 realm = 'trac' 78 123 79 124 # build the options … … 84 129 parser.add_option("-p", "--password",action="store", dest="password", type = "string", 85 130 help="the password to use") 131 parser.add_option("-r", "--realm",action="store", dest="realm", type = "string", 132 help="the realm in which to create the digest") 86 133 (options, args) = parser.parse_args() 87 134 … … 89 136 if (options.username is None) or (options.password is None): 90 137 parser.error("You must supply both the username and password") 138 if (options.realm is not None): 139 realm = options.realm 91 140 92 141 # Generate the string to enter into the htdigest file 93 realm = 'trac' 94 kd = lambda x: md5.md5(':'.join(x)).hexdigest() 142 kd = lambda x: md5(':'.join(x)).hexdigest() 95 143 print ':'.join((options.username, realm, kd([options.username, realm, options.password]))) 96 144 }}} … … 100 148 {{{ 101 149 python trac-digest.py -u username -p password >> c:\digest.txt 102 python tracd --port 8000 --authproj_name,c:\digest.txt,trac c:\path\to\proj_name150 tracd --port 8000 --auth=proj_name,c:\digest.txt,trac c:\path\to\proj_name 103 151 }}} 152 153 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.) 154 155 It is possible to use md5sum utility to generate digest-password file using such method: 156 {{{ 157 echo -e "${user}:trac:${password}\c" | md5sum - >>to-file 158 }}} 159 and manually delete " -" from the end and add "${user}:trac:" to the start of line from 'to-file'. You can see attachment:trac-digest-corrected.sh for detail. 104 160 105 161 == Tips == … … 123 179 `htdocs:software-0.1.tar.gz`. 124 180 125 ---- 126 See also: TracInstall, TracCgi, TracModPython, TracGuide 181 === Using apache rewrite rules === 182 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. 183 184 === Serving a different base path than / === 185 Tracd supports serving projects with different base urls than /<project>. The parameter name to change this is 186 {{{ 187 tracd --base-path=/some/path 188 }}} 127 189 128 190 ---- 129 '''Translation:''' 130 * [https://opensvn.csie.org/traccgi/trac_rus/wiki/StandAloneTracForTeapot Russian] (перевод на Русский) 191 See also: TracInstall, TracCgi, TracModPython, TracGuide, [trac:TracOnWindowsStandalone?version=13#RunningTracdasservice Running tracd.exe as a Windows service]
