Fossil SCM
Small clarity tweak to the new "Methods" discussion in www/server.wiki.
Commit
fc00b7b2972a81dfc57c247d61586ebf5237c918e2a9fa199e11a0bf5f3d1810
Parent
0bb59100f2d9330…
1 file changed
+8
-2
+8
-2
| --- www/server.wiki | ||
| +++ www/server.wiki | ||
| @@ -41,12 +41,18 @@ | ||
| 41 | 41 | <li><a id="standalone" href="./server/any/none.md">Stand-alone HTTP server</a> |
| 42 | 42 | <li><a id="scgi" href="./server/any/scgi.md">SCGI</a> |
| 43 | 43 | <li><a id="cgi" href="./server/any/cgi.md">CGI</a> |
| 44 | 44 | </ol> |
| 45 | 45 | |
| 46 | -The HTTP and SCGI options also allow for various sorts of reverse | |
| 47 | -proxying: Apache, nginx, HAProxy, stunnel (proxy mode), IIS... | |
| 46 | +Fossil's HTTP server can be used standalone or you can put it behind | |
| 47 | +many different pieces of software via various proxying schemes: Apache, | |
| 48 | +nginx, HAProxy, stunnel (proxy mode), IIS... We cover some of those | |
| 49 | +options below. | |
| 50 | + | |
| 51 | +The CGI option works with many different web servers: Apache, IIS, | |
| 52 | +<tt>lighttpd</tt>, <tt>althttpd</tt>... Where CGI doesn't work, SCGI | |
| 53 | +usually does instead, such as in nginx. | |
| 48 | 54 | |
| 49 | 55 | Regardless of the method you choose, all can serve either a single repository |
| 50 | 56 | or a directory hierarchy containing many repositories with names ending in ".fossil". |
| 51 | 57 | |
| 52 | 58 | We've broken the configuration for each method out into a series of |
| 53 | 59 |
| --- www/server.wiki | |
| +++ www/server.wiki | |
| @@ -41,12 +41,18 @@ | |
| 41 | <li><a id="standalone" href="./server/any/none.md">Stand-alone HTTP server</a> |
| 42 | <li><a id="scgi" href="./server/any/scgi.md">SCGI</a> |
| 43 | <li><a id="cgi" href="./server/any/cgi.md">CGI</a> |
| 44 | </ol> |
| 45 | |
| 46 | The HTTP and SCGI options also allow for various sorts of reverse |
| 47 | proxying: Apache, nginx, HAProxy, stunnel (proxy mode), IIS... |
| 48 | |
| 49 | Regardless of the method you choose, all can serve either a single repository |
| 50 | or a directory hierarchy containing many repositories with names ending in ".fossil". |
| 51 | |
| 52 | We've broken the configuration for each method out into a series of |
| 53 |
| --- www/server.wiki | |
| +++ www/server.wiki | |
| @@ -41,12 +41,18 @@ | |
| 41 | <li><a id="standalone" href="./server/any/none.md">Stand-alone HTTP server</a> |
| 42 | <li><a id="scgi" href="./server/any/scgi.md">SCGI</a> |
| 43 | <li><a id="cgi" href="./server/any/cgi.md">CGI</a> |
| 44 | </ol> |
| 45 | |
| 46 | Fossil's HTTP server can be used standalone or you can put it behind |
| 47 | many different pieces of software via various proxying schemes: Apache, |
| 48 | nginx, HAProxy, stunnel (proxy mode), IIS... We cover some of those |
| 49 | options below. |
| 50 | |
| 51 | The CGI option works with many different web servers: Apache, IIS, |
| 52 | <tt>lighttpd</tt>, <tt>althttpd</tt>... Where CGI doesn't work, SCGI |
| 53 | usually does instead, such as in nginx. |
| 54 | |
| 55 | Regardless of the method you choose, all can serve either a single repository |
| 56 | or a directory hierarchy containing many repositories with names ending in ".fossil". |
| 57 | |
| 58 | We've broken the configuration for each method out into a series of |
| 59 |