| | @@ -206,30 +206,17 @@ |
| 206 | 206 | <h2 id="server">Fossil TLS Configuration: Server Side</h2> |
| 207 | 207 | |
| 208 | 208 | Fossil's built-in HTTP server feature does not currently have a built-in |
| 209 | 209 | way to serve via HTTP over TLS, a.k.a. HTTPS, even when you've linked |
| 210 | 210 | Fossil to OpenSSL. To serve a Fossil repository via HTTPS, you must put |
| 211 | | -it behind some kind of HTTPS proxy. |
| 212 | | - |
| 213 | | - |
| 214 | | -<h3 id="stunnel">stunnel Alone</h3> |
| 215 | | - |
| 216 | | -That's covered [./server/any/stunnel.md | elsewhere]. |
| 217 | | - |
| 218 | | - |
| 219 | | -<h3 id="althttpd">stunnel + althttpd</h3> |
| 220 | | - |
| 221 | | -That's covered [./server/any/althttpd.md | elsewhere]. |
| 222 | | - |
| 223 | | - |
| 224 | | -<h3 id="nginx">nginx</h3> |
| 225 | | - |
| 226 | | -If your needs are more complex than althttpd can handle or you'd prefer |
| 227 | | -to use only software available in your server operating system's package |
| 228 | | -repository, we recommend that you step up to [http://nginx.org/|nginx]. |
| 229 | | -Setting this up is complex enough that we cover it [./tls-nginx.md|in a |
| 230 | | -separate document]. |
| 211 | +it behind some kind of HTTPS proxy. We have a number of documents |
| 212 | +elsewhere in this repository that cover your options for [./server.wiki |
| 213 | +| serving Fossil repositories]. A few of the most useful of these are: |
| 214 | + |
| 215 | + * <a id="stunnel" href="./server/any/stunnel.md">Serving via stunnel</a> |
| 216 | + * <a id="althttpd" href="./server/any/althttpd.md">Serving via stunnel + althttpd</a> |
| 217 | + * <a id="nginx" href="./server/any/scgi.md">Serving via SCGI (nginx)</a> |
| 231 | 218 | |
| 232 | 219 | |
| 233 | 220 | <h2 id="enforcing">Enforcing TLS Access</h2> |
| 234 | 221 | |
| 235 | 222 | To use TLS encryption in cloning and syncing to a remote Fossil |
| 236 | 223 | |