Changes between Version 3 and Version 4 of 0.12/TracStandalone

Timestamp:

Mar 23, 2010, 3:35:47 PM (14 years ago)

Author:

mark.m.mcmahon@…

Comment:

Reviewed. Need input for one area regarding htpasswd -m parameter.

0.12/TracStandalone

@@ -77 +77 @@
 }}}
 
-What is environmentname? I have looked in my trac.ini and there is no environmentname, there is a project name. Is project name the same as environment name? Are the two interchangeable? Looking at the directory structure created for my project I don't have a sub directory for the environment name (what ever that may be - if I have read your documentation correctly it is the same as the project name). So how can I link to an .htpaswd file that is not there?
-
+ `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.
 
 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.)
@@ -169 +168 @@
 }}}
 
+{{{#!div style="background:#efe"
+Testing on or confirmation for *nix required in below paragraph.
+
+The -m option referred to from httpasswd is ...
+     -m   Use Apache's  modified  MD5  algorithm  for  passwords.
+          Passwords  encrypted with this algorithm are transport-
+          able to any platform (Windows, Unix, BeOS,  et  cetera)
+          running  Apache  1.3.9  or  later.  On Windows and TPF,
+          this flag is the default.
+}}}
+
 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.)
 
@@ -181 +191 @@
 === Serving static content ===
 
-If `tracd` is the only webserver used for the project, 
+If `tracd` is the only web server used for the project, 
 it can also be used to distribute static content 
 (tarballs, Doxygen documentation, etc.)
@@ -190 +200 @@
 Example: given a `$TRAC_ENV/htdocs/software-0.1.tar.gz` file,
 the corresponding relative URL would be `/<project_name>/chrome/site/software-0.1.tar.gz`, 
-which in turn can be written using the relative link syntax
-in the Wiki: `[/<project_name>/chrome/site/software-0.1.tar.gz]` 
-
-Since 0.10, Trac supports a new `htdocs:` TracLinks 
-syntax for the above. With this, the example link above can be written simply 
-`htdocs:software-0.1.tar.gz`. 
+which in turn can be written as `htdocs:software-0.1.tar.gz` (TracLinks syntax) or `[/<project_name>/chrome/site/software-0.1.tar.gz]` (relative link syntax). 
+
+ ''Support for `htdocs:` TracLinks syntax was added in version 0.10''
 
 === Using apache rewrite rules ===