102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
|
HTTP requests from clients, you configure a socket listener daemon to
run a <a href="/help?cmd=http"><tt>fossil http</tt></a> command on each
HTTP hit. That Fossil instance handles only that one hit and then shuts
back down, letting the socket listener go back to waiting for the next
hit. This scheme is known to work with <a id="inetd"
href="any/inetd.md"><tt>inetd</tt></a>, <a id="xinetd"
href="any/xinetd.md"><tt>xinetd</tt></a>, <a id="stunnel"
href="any/stunnel.md"><tt>stunnel</tt></a>, and <a
href="debian/service.md"><tt>systemd</tt></a>.</p>
<p>In principle, this method should also work with Apple’s
<tt>launchd</tt> and Solaris’ SMF
which have similar socket listener features. We
we welcome <a href="contribute.wiki">contributions</a> of such tutorials.</p>
|
|
>
<
<
<
<
<
|
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
|
HTTP requests from clients, you configure a socket listener daemon to
run a <a href="/help?cmd=http"><tt>fossil http</tt></a> command on each
HTTP hit. That Fossil instance handles only that one hit and then shuts
back down, letting the socket listener go back to waiting for the next
hit. This scheme is known to work with <a id="inetd"
href="any/inetd.md"><tt>inetd</tt></a>, <a id="xinetd"
href="any/xinetd.md"><tt>xinetd</tt></a>, <a id="stunnel"
href="any/stunnel.md"><tt>stunnel</tt></a>, <a
href="macos/service.md"><tt>launchd</tt></a>, and <a
href="debian/service.md"><tt>systemd</tt></a>.</p>
<h3>SCGI</h3>
<p>The Fossil standalone server can also run <a href="any/scgi.md">in
SCGI mode</a> — <a href="/help/server"><tt>fossil server --scgi</tt></a>
— instead of <a href="any/none.md">HTTP mode</a>, which allows it to
respond to requests from web servers <a href="debian/nginx.md">such as
|