Fossil SCM

docs: a typo fix and an updated date reference.

stephan 2022-02-21 20:54 trunk
Commit 841c78d2cd94b193e34fac6dfd15b1d6e41fa62723215872ccd7f9b1a013d6f1
2 files changed +1 -1 +6 -5
+1 -1
--- www/chat.md
+++ www/chat.md
@@ -136,11 +136,11 @@
136136
The [fossil chat send](/help?cmd=chat) can be used by project-specific
137137
robots to send notifications to the chatroom. For example, on the
138138
[SQLite project](https://sqlite.org/) (for which the Fossil chatroom
139139
feature, and indeed all of Fossil, was invented) there are long-running
140140
fuzz servers that sometimes run across obscure problems. Whenever this
141
-happens, a message is sent to the SQLite developers chatroom altering
141
+happens, a message is sent to the SQLite developers chatroom alerting
142142
them to the problem.
143143
144144
The recommended way to allow robots to send chat messages is to create
145145
a new user on the server for each robot. Give each such robot account
146146
the "C" privilege only. That means that the robot user account will be
147147
--- www/chat.md
+++ www/chat.md
@@ -136,11 +136,11 @@
136 The [fossil chat send](/help?cmd=chat) can be used by project-specific
137 robots to send notifications to the chatroom. For example, on the
138 [SQLite project](https://sqlite.org/) (for which the Fossil chatroom
139 feature, and indeed all of Fossil, was invented) there are long-running
140 fuzz servers that sometimes run across obscure problems. Whenever this
141 happens, a message is sent to the SQLite developers chatroom altering
142 them to the problem.
143
144 The recommended way to allow robots to send chat messages is to create
145 a new user on the server for each robot. Give each such robot account
146 the "C" privilege only. That means that the robot user account will be
147
--- www/chat.md
+++ www/chat.md
@@ -136,11 +136,11 @@
136 The [fossil chat send](/help?cmd=chat) can be used by project-specific
137 robots to send notifications to the chatroom. For example, on the
138 [SQLite project](https://sqlite.org/) (for which the Fossil chatroom
139 feature, and indeed all of Fossil, was invented) there are long-running
140 fuzz servers that sometimes run across obscure problems. Whenever this
141 happens, a message is sent to the SQLite developers chatroom alerting
142 them to the problem.
143
144 The recommended way to allow robots to send chat messages is to create
145 a new user on the server for each robot. Give each such robot account
146 the "C" privilege only. That means that the robot user account will be
147
+6 -5
--- www/ssl.wiki
+++ www/ssl.wiki
@@ -227,15 +227,16 @@
227227
228228
229229
<h2 id="server">Fossil TLS Configuration: Server Side</h2>
230230
231231
Fossil's built-in HTTP server feature did not add [./ssl-server.md|support HTTP over TLS]
232
-(a.k.a. HTTPS) until version 2.18 (2022). Prior to that, system administrators
233
-that wanted to add HTTPS support to a Fossil server had to put Fossil
234
-behind a web-server or reverse-proxy that would do the HTTPS to HTTP
235
-translation. [./server/ | Instructions for doing so] are found elsewhere
236
-in this documentation. A few of the most useful of these are:
232
+(a.k.a. HTTPS) until version 2.18 (early 2022). Prior to that, system
233
+administrators that wanted to add HTTPS support to a Fossil server had
234
+to put Fossil behind a web-server or reverse-proxy that would do the
235
+HTTPS to HTTP translation. [./server/ | Instructions for doing so]
236
+are found elsewhere in this documentation. A few of the most useful
237
+of these are:
237238
238239
* <a id="stunnel" href="./server/any/stunnel.md">Serving via stunnel</a>
239240
* <a id="althttpd" href="./server/any/althttpd.md">Serving via stunnel + althttpd</a>
240241
* <a id="nginx" href="./server/debian/nginx.md#tls">Serving via SCGI with nginx on Debian</a>
241242
242243
--- www/ssl.wiki
+++ www/ssl.wiki
@@ -227,15 +227,16 @@
227
228
229 <h2 id="server">Fossil TLS Configuration: Server Side</h2>
230
231 Fossil's built-in HTTP server feature did not add [./ssl-server.md|support HTTP over TLS]
232 (a.k.a. HTTPS) until version 2.18 (2022). Prior to that, system administrators
233 that wanted to add HTTPS support to a Fossil server had to put Fossil
234 behind a web-server or reverse-proxy that would do the HTTPS to HTTP
235 translation. [./server/ | Instructions for doing so] are found elsewhere
236 in this documentation. A few of the most useful of these are:
 
237
238 * <a id="stunnel" href="./server/any/stunnel.md">Serving via stunnel</a>
239 * <a id="althttpd" href="./server/any/althttpd.md">Serving via stunnel + althttpd</a>
240 * <a id="nginx" href="./server/debian/nginx.md#tls">Serving via SCGI with nginx on Debian</a>
241
242
--- www/ssl.wiki
+++ www/ssl.wiki
@@ -227,15 +227,16 @@
227
228
229 <h2 id="server">Fossil TLS Configuration: Server Side</h2>
230
231 Fossil's built-in HTTP server feature did not add [./ssl-server.md|support HTTP over TLS]
232 (a.k.a. HTTPS) until version 2.18 (early 2022). Prior to that, system
233 administrators that wanted to add HTTPS support to a Fossil server had
234 to put Fossil behind a web-server or reverse-proxy that would do the
235 HTTPS to HTTP translation. [./server/ | Instructions for doing so]
236 are found elsewhere in this documentation. A few of the most useful
237 of these are:
238
239 * <a id="stunnel" href="./server/any/stunnel.md">Serving via stunnel</a>
240 * <a id="althttpd" href="./server/any/althttpd.md">Serving via stunnel + althttpd</a>
241 * <a id="nginx" href="./server/debian/nginx.md#tls">Serving via SCGI with nginx on Debian</a>
242
243

Keyboard Shortcuts

Open search /
Next entry (timeline) j
Previous entry (timeline) k
Open focused entry Enter
Show this help ?
Toggle theme Top nav button