Changes between Version 5 and Version 6 of TracStandalone

Timestamp:

2021-07-11T14:17:48-07:00 (3 years ago)

Author:

trac

Comment:

--

TracStandalone

@@ -46 +46 @@
 
 === Option 1
-To install as a Windows service, get the [http://www.google.com/search?q=srvany.exe SRVANY] utility and run:
+To install as a Windows service, get the [https://www.google.com/search?q=srvany.exe SRVANY] utility and run:
 {{{#!cmd
  C:\path\to\instsrv.exe tracd C:\path\to\srvany.exe
@@ -77 +77 @@
 }}}
 
-For 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:
+For Windows 7 User, srvany.exe may not be an option, so you can use [https://www.google.com/search?q=winserv.exe WINSERV] utility and run:
 {{{#!cmd
 "C:\path\to\winserv.exe" install tracd -displayname "tracd" -start auto "C:\path\to\python.exe" c:\path\to\python\scripts\tracd.exe <your tracd parameters>"
@@ -85 +85 @@
 === Option 2
 
-Use [http://trac-hacks.org/wiki/WindowsServiceScript WindowsServiceScript], available at [http://trac-hacks.org/ Trac Hacks]. Installs, removes, starts, stops, etc. your Trac service.
+Use [https://trac-hacks.org/wiki/WindowsServiceScript WindowsServiceScript], available at [https://trac-hacks.org/ Trac Hacks]. Installs, removes, starts, stops, etc. your Trac service.
 
 === Option 3
@@ -171 +171 @@
 === Digest authentication: Using a htdigest password file
 
-If 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.
+If you have Apache available, you can use the htdigest command to generate the password file. Type 'htdigest' to get some usage instructions, or read [https://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.
 
 Note that you can start tracd without the `--auth` argument, but if you click on the ''Login'' link you will get an error.
@@ -208 +208 @@
              [--protocol {http,https,scgi,ajp,fcgi}] [--certfile CERTFILE]
              [--keyfile KEYFILE] [-q] [--base-path BASE_PATH]
-             [--http10 | --http11] [-r | -d] [--pidfile PIDFILE]
-             [--umask MASK] [--group GROUP] [--user USER]
-             [envs [envs ...]]
+             [--http10 | --http11] [-r | -d] [--pidfile PIDFILE] [--umask MASK]
+             [--group GROUP] [--user USER]
+             [envs ...]
 
 positional arguments:
@@ -253 +253 @@
 === Serving static content
 
-If `tracd` is the only web server used for the project, 
-it can also be used to distribute static content 
+If `tracd` is the only web server used for the project,
+it can also be used to distribute static content
 (tarballs, Doxygen documentation, etc.)
 
@@ -261 +261 @@
 
 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`, 
+the corresponding relative URL would be `/<project_name>/chrome/site/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).
 
@@ -301 +301 @@
     implements(IAuthenticator)
 
-    obey_remote_user_header = BoolOption('trac', 'obey_remote_user_header', 'false', 
-               """Whether the 'Remote-User:' HTTP header is to be trusted for user logins 
-                (''since ??.??').""") 
+    obey_remote_user_header = BoolOption('trac', 'obey_remote_user_header', 'false',
+               """Whether the 'Remote-User:' HTTP header is to be trusted for user logins
+                (''since ??.??').""")
 
     def authenticate(self, req):
-        if self.obey_remote_user_header and req.get_header('Remote-User'): 
-            return req.get_header('Remote-User') 
+        if self.obey_remote_user_header and req.get_header('Remote-User'):
+            return req.get_header('Remote-User')
         return None