Bienvenue sur PostGIS.fr

Bienvenue sur PostGIS.fr , le site de la communauté des utilisateurs francophones de PostGIS.

PostGIS ajoute le support d'objets géographique à la base de données PostgreSQL. En effet, PostGIS "spatialise" le serverur PostgreSQL, ce qui permet de l'utiliser comme une base de données SIG.

Maintenu à jour, en fonction de nos disponibilités et des diverses sorties des outils que nous testons, nous vous proposons l'ensemble de nos travaux publiés en langue française.

Changes between Version 1 and Version 2 of TracStandalone


Ignore:
Timestamp:
21/09/2011 11:27:42 (13 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracStandalone

    v1 v2  
    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{{{ 
     
    7386== Using Authentication == 
    7487 
    75 Using tracd with Apache .htpasswd files: 
    76  
    77 To create a .htpasswd file using htpasswd: 
    78  
    79 {{{ 
    80  $ sudo htpasswd -c /path/to/env/.htpasswd username 
    81 }}} 
    82 then for additional users: 
    83 {{{ 
    84  $ sudo 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  
     88Tracd 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. 
     89 
     90The general format for using authentication is: 
    9991{{{ 
    10092 $ tracd -p port --auth="base_project_dir,password_file_path,realm" project_path 
    10193}}} 
    102  
    10394where: 
    104  
    10595 * '''base_project_dir''': the base directory of the project specified as follows: 
    106    * when serving multiple projects: ''relative'' to the `project_bath` 
     96   * when serving multiple projects: ''relative'' to the `project_path` 
    10797   * when serving only a single project (`-s`): the name of the project directory 
    10898 Don't use an absolute path here as this won't work. ''Note:'' This parameter is case-sensitive even for environments on Windows. 
     
    111101 * '''project_path''': path of the project 
    112102 
     103 * **`--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. 
     104 
    113105Examples: 
    114106 
     
    133125}}} 
    134126 
    135 === Using a htpasswd password file === 
     127=== Basic Authorization: Using a htpasswd password file === 
    136128This section describes how to use `tracd` with Apache .htpasswd files. 
    137129 
    138130To create a .htpasswd file use Apache's `htpasswd` command (see [#GeneratingPasswordsWithoutApache below] for a method to create these files without using Apache): 
    139  
    140131{{{ 
    141132 $ sudo htpasswd -c /path/to/env/.htpasswd username 
     
    147138 
    148139Then to start `tracd` run something like this: 
    149  
    150140{{{ 
    151141 $ tracd -p 8080 --basic-auth="projectdirname,/fullpath/environmentname/.htpasswd,realmname" /fullpath/environmentname 
     
    153143 
    154144For example: 
    155  
    156145{{{ 
    157146 $ tracd -p 8080 --basic-auth="testenv,/srv/tracenv/testenv/.htpasswd,My Test Env" /srv/tracenv/testenv 
    158147}}} 
    159  
    160148''Note:'' You might need to pass "-m" as a parameter to htpasswd on some platforms (OpenBSD). 
    161149 
    162 === Using a htdigest password file === 
     150=== Digest authentication: Using a htdigest password file === 
    163151 
    164152If 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. 
     
    168156=== Generating Passwords Without Apache === 
    169157 
    170 If you don't have Apache available, you can use this simple Python script to generate your passwords: 
     158Basic Authorization can be accomplished via this [http://www.4webhelp.net/us/password.php online HTTP Password generator].  Copy the generated password-hash line to the .htpasswd file on your system. 
     159 
     160You can use this simple Python script to generate a '''digest''' password file: 
    171161 
    172162{{{ 
     
    202192}}} 
    203193 
    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): 
     194Note: 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): 
    205195 
    206196{{{ 
     
    209199}}} 
    210200 
    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: 
     201==== Using `md5sum` 
     202It is possible to use `md5sum` utility to generate digest-password file: 
    215203{{{ 
    216204 $ printf "${user}:trac:${password}" | md5sum - >>user.htdigest 
    217205}}} 
    218206and manually delete " -" from the end and add "${user}:trac:" to the start of line from 'to-file'. 
     207 
     208== Reference == 
     209 
     210Here's the online help, as a reminder (`tracd --help`): 
     211{{{ 
     212Usage: tracd [options] [projenv] ... 
     213 
     214Options: 
     215  --version             show program's version number and exit 
     216  -h, --help            show this help message and exit 
     217  -a DIGESTAUTH, --auth=DIGESTAUTH 
     218                        [projectdir],[htdigest_file],[realm] 
     219  --basic-auth=BASICAUTH 
     220                        [projectdir],[htpasswd_file],[realm] 
     221  -p PORT, --port=PORT  the port number to bind to 
     222  -b HOSTNAME, --hostname=HOSTNAME 
     223                        the host name or IP address to bind to 
     224  --protocol=PROTOCOL   http|scgi|ajp 
     225  -q, --unquote         unquote PATH_INFO (may be needed when using ajp) 
     226  --http10              use HTTP/1.0 protocol version (default) 
     227  --http11              use HTTP/1.1 protocol version instead of HTTP/1.0 
     228  -e PARENTDIR, --env-parent-dir=PARENTDIR 
     229                        parent directory of the project environments 
     230  --base-path=BASE_PATH 
     231                        the initial portion of the request URL's "path" 
     232  -r, --auto-reload     restart automatically when sources are modified 
     233  -s, --single-env      only serve a single project without the project list 
     234}}} 
    219235 
    220236== Tips == 
     
    235251 ''Support for `htdocs:` TracLinks syntax was added in version 0.10'' 
    236252 
    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. 
     253=== Using tracd behind a proxy 
     254 
     255In some situations when you choose to use tracd behind Apache or another web server. 
     256 
     257In 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. 
     258 
     259If 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. 
     260 
     261See also [trac:TracOnWindowsIisAjp], [trac:TracNginxRecipe]. 
    239262 
    240263=== Serving a different base path than / === 
     
    245268 
    246269---- 
    247 See also: TracInstall, TracCgi, TracModPython, TracGuide, [trac:TracOnWindowsStandalone?version=13#RunningTracdasservice Running tracd.exe as a Windows service], [trac:TracOnWindowsIisAjp], [trac:TracNginxRecipe] 
     270See also: TracInstall, TracCgi, TracModPython, TracGuide, [trac:TracOnWindowsStandalone#RunningTracdasservice Running tracd.exe as a Windows service]