Fossil SCM
Corrected the description of nginx + SCGI in www/server.wiki.
Commit
0f217e89f27e80e8c3fac34b01b2b05998d1b890fbf6189d45f13252a0329391
Parent
fbacfacfe6939a4…
1 file changed
+5
-6
+5
-6
| --- www/server.wiki | ||
| +++ www/server.wiki | ||
| @@ -47,17 +47,16 @@ | ||
| 47 | 47 | A [/help?cmd=cgi|short CGI script] is placed in the document |
| 48 | 48 | hierarchy of the web server, and when a client requests the |
| 49 | 49 | appropriate URL, Fossil is run to generate the responce. |
| 50 | 50 | CGI is a good choice for incorporating Fossil as part of a |
| 51 | 51 | larger website. The Fossil [./selfhost.wiki|self-hosting repositories] |
| 52 | -are implemented CGI running behind althttpd. | |
| 52 | +are implemented with CGI underneath althttpd. | |
| 53 | 53 | |
| 54 | -For web servers such as Nginx that do not support | |
| 55 | -CGI, Fossil can be run using SCGI. SCGI involves running | |
| 56 | -the [/help?cmd=http|fossil http] command with the --scgi | |
| 57 | -option. SCGI is something of a cross between a stand-alone server | |
| 58 | -running behind a reverse proxy and an ordinary CGI server. | |
| 54 | +For web servers such as nginx that do not support CGI, Fossil supports | |
| 55 | +SCGI, a protocol that gives most of the simplicity of CGI with the | |
| 56 | +efficiency of the stand-alone server option. With nginx, you use the | |
| 57 | +[/help/server|fossil server] command with the --scgi option. | |
| 59 | 58 | |
| 60 | 59 | Regardless of the method you choose, all can serve either a single |
| 61 | 60 | repository or a directory hierarchy containing many repositories |
| 62 | 61 | with names ending in ".fossil". |
| 63 | 62 | |
| 64 | 63 |
| --- www/server.wiki | |
| +++ www/server.wiki | |
| @@ -47,17 +47,16 @@ | |
| 47 | A [/help?cmd=cgi|short CGI script] is placed in the document |
| 48 | hierarchy of the web server, and when a client requests the |
| 49 | appropriate URL, Fossil is run to generate the responce. |
| 50 | CGI is a good choice for incorporating Fossil as part of a |
| 51 | larger website. The Fossil [./selfhost.wiki|self-hosting repositories] |
| 52 | are implemented CGI running behind althttpd. |
| 53 | |
| 54 | For web servers such as Nginx that do not support |
| 55 | CGI, Fossil can be run using SCGI. SCGI involves running |
| 56 | the [/help?cmd=http|fossil http] command with the --scgi |
| 57 | option. SCGI is something of a cross between a stand-alone server |
| 58 | running behind a reverse proxy and an ordinary CGI server. |
| 59 | |
| 60 | Regardless of the method you choose, all can serve either a single |
| 61 | repository or a directory hierarchy containing many repositories |
| 62 | with names ending in ".fossil". |
| 63 | |
| 64 |
| --- www/server.wiki | |
| +++ www/server.wiki | |
| @@ -47,17 +47,16 @@ | |
| 47 | A [/help?cmd=cgi|short CGI script] is placed in the document |
| 48 | hierarchy of the web server, and when a client requests the |
| 49 | appropriate URL, Fossil is run to generate the responce. |
| 50 | CGI is a good choice for incorporating Fossil as part of a |
| 51 | larger website. The Fossil [./selfhost.wiki|self-hosting repositories] |
| 52 | are implemented with CGI underneath althttpd. |
| 53 | |
| 54 | For web servers such as nginx that do not support CGI, Fossil supports |
| 55 | SCGI, a protocol that gives most of the simplicity of CGI with the |
| 56 | efficiency of the stand-alone server option. With nginx, you use the |
| 57 | [/help/server|fossil server] command with the --scgi option. |
| 58 | |
| 59 | Regardless of the method you choose, all can serve either a single |
| 60 | repository or a directory hierarchy containing many repositories |
| 61 | with names ending in ".fossil". |
| 62 | |
| 63 |