Fossil SCM
Updated www/server/index.html to no longer discuss launchd as a "maybe" option now that we have a document for it, and removed mention of Solaris SMF entirely.
Commit
1e6fbcf214e4b8d1eb05c0c5501172e7fb4c1a2809d120ae2d52e89d98d93754
Parent
e0ad4b48b5a7c5c…
1 file changed
+2
-6
+2
-6
| --- www/server/index.html | ||
| +++ www/server/index.html | ||
| @@ -104,18 +104,14 @@ | ||
| 104 | 104 | HTTP hit. That Fossil instance handles only that one hit and then shuts |
| 105 | 105 | back down, letting the socket listener go back to waiting for the next |
| 106 | 106 | hit. This scheme is known to work with <a id="inetd" |
| 107 | 107 | href="any/inetd.md"><tt>inetd</tt></a>, <a id="xinetd" |
| 108 | 108 | href="any/xinetd.md"><tt>xinetd</tt></a>, <a id="stunnel" |
| 109 | -href="any/stunnel.md"><tt>stunnel</tt></a>, and <a | |
| 109 | +href="any/stunnel.md"><tt>stunnel</tt></a>, <a | |
| 110 | +href="macos/service.md"><tt>launchd</tt></a>, and <a | |
| 110 | 111 | href="debian/service.md"><tt>systemd</tt></a>.</p> |
| 111 | 112 | |
| 112 | -<p>In principle, this method should also work with Apple’s | |
| 113 | -<tt>launchd</tt> and Solaris’ SMF | |
| 114 | -which have similar socket listener features. We | |
| 115 | -we welcome <a href="contribute.wiki">contributions</a> of such tutorials.</p> | |
| 116 | - | |
| 117 | 113 | |
| 118 | 114 | <h3>SCGI</h3> |
| 119 | 115 | |
| 120 | 116 | <p>The Fossil standalone server can also run <a href="any/scgi.md">in |
| 121 | 117 | SCGI mode</a> — <a href="/help/server"><tt>fossil server --scgi</tt></a> |
| 122 | 118 |
| --- www/server/index.html | |
| +++ www/server/index.html | |
| @@ -104,18 +104,14 @@ | |
| 104 | HTTP hit. That Fossil instance handles only that one hit and then shuts |
| 105 | back down, letting the socket listener go back to waiting for the next |
| 106 | hit. This scheme is known to work with <a id="inetd" |
| 107 | href="any/inetd.md"><tt>inetd</tt></a>, <a id="xinetd" |
| 108 | href="any/xinetd.md"><tt>xinetd</tt></a>, <a id="stunnel" |
| 109 | href="any/stunnel.md"><tt>stunnel</tt></a>, and <a |
| 110 | href="debian/service.md"><tt>systemd</tt></a>.</p> |
| 111 | |
| 112 | <p>In principle, this method should also work with Apple’s |
| 113 | <tt>launchd</tt> and Solaris’ SMF |
| 114 | which have similar socket listener features. We |
| 115 | we welcome <a href="contribute.wiki">contributions</a> of such tutorials.</p> |
| 116 | |
| 117 | |
| 118 | <h3>SCGI</h3> |
| 119 | |
| 120 | <p>The Fossil standalone server can also run <a href="any/scgi.md">in |
| 121 | SCGI mode</a> — <a href="/help/server"><tt>fossil server --scgi</tt></a> |
| 122 |
| --- www/server/index.html | |
| +++ www/server/index.html | |
| @@ -104,18 +104,14 @@ | |
| 104 | HTTP hit. That Fossil instance handles only that one hit and then shuts |
| 105 | back down, letting the socket listener go back to waiting for the next |
| 106 | hit. This scheme is known to work with <a id="inetd" |
| 107 | href="any/inetd.md"><tt>inetd</tt></a>, <a id="xinetd" |
| 108 | href="any/xinetd.md"><tt>xinetd</tt></a>, <a id="stunnel" |
| 109 | href="any/stunnel.md"><tt>stunnel</tt></a>, <a |
| 110 | href="macos/service.md"><tt>launchd</tt></a>, and <a |
| 111 | href="debian/service.md"><tt>systemd</tt></a>.</p> |
| 112 | |
| 113 | |
| 114 | <h3>SCGI</h3> |
| 115 | |
| 116 | <p>The Fossil standalone server can also run <a href="any/scgi.md">in |
| 117 | SCGI mode</a> — <a href="/help/server"><tt>fossil server --scgi</tt></a> |
| 118 |