30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
|
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
|
-
+
|
<h2 id="methods">Methods</h2>
<blockquote>
There are basically four ways to set up a Fossil server:
<ol>
<li>Socket activation:
<li>Socket listener:
<a id="inetd" href="./server/any/inetd.md">inetd</a>,
<a id="xinetd" href="./server/any/xinetd.md">xinetd</a>,
<a id="stunnel" href="./server/any/stunnel.md">stunnel</a>...
<li><a id="standalone" href="./server/any/none.md">Stand-alone HTTP server</a>
<li><a id="scgi" href="./server/any/scgi.md">SCGI</a>
<li><a id="cgi" href="./server/any/cgi.md">CGI</a>
</ol>
|
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
|
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
|
-
+
|
<blockquote>
Where there is a check mark in the "Any" row, the method for that is
generic enough that it works across OSes that Fossil is known to work
on. The check marks below that usually just link to this generic
documentation.
There are several widely-deployed socket activation schemes besides the
There are several widely-deployed socket listener schemes besides the
<tt>inetd</tt>, <tt>xinetd</tt>, and <tt>stunnel</tt> schemes with
documents linked above: Apple’s <tt>launchd</tt>, Linux’s
<tt>systemd</tt>, Solaris’ SMF, etc. We would welcome [./contribute.wiki
| contributions] to cover these as well. We also welcome contributions
to fill gaps (❌) in the table above.
</blockquote>
|