Fossil SCM

Update the server documentation to show an example stunnel4 configuration.

drh 2013-10-04 16:42 trunk
Commit bd6dac51d1446c307395530a4c7ad9c1937d1fde
1 file changed +13 -1
+13 -1
--- www/server.wiki
+++ www/server.wiki
@@ -102,11 +102,23 @@
102102
[http://www.stunnel.org/ | Stunnel version 4] is an inetd-like process that
103103
accepts and decodes SSL-encrypted connections. Fossil can be run directly from
104104
stunnel in a mannar similar to inetd and xinetd. This can be used to provide
105105
a secure link to a Fossil project. The configuration needed to get stunnel4
106106
to invoke Fossil is very similar to the inetd and xinetd examples shown above.
107
-See the stunnel4 documentation for details.
107
+The relevant parts of an stunnel configuration might look something
108
+like the following:
109
+<blockquote><pre><nowiki>
110
+[https]
111
+accept = www.ubercool-project.org:443
112
+TIMEOUTclose = 0
113
+exec = /usr/bin/fossil
114
+execargs = /usr/bin/fossil http /home/fossil/ubercool.fossil --https
115
+</nowiki></pre></blockquote>
116
+See the stunnel4 documentation for further details bout the /etc/stunnel/stunnel.conf
117
+configuration file. Note that the [fossil http] command should include the --https
118
+option to let Fossil know to use "https" instead of "http" as the scheme on generated
119
+hyperlinks.
108120
<p>
109121
Using inetd or xinetd or stunnel is a more complex setup
110122
than the "standalone" server, but it has the
111123
advantage of only using system resources when an actual connection is
112124
attempted. If no-one ever connects to that port, a Fossil server will
113125
--- www/server.wiki
+++ www/server.wiki
@@ -102,11 +102,23 @@
102 [http://www.stunnel.org/ | Stunnel version 4] is an inetd-like process that
103 accepts and decodes SSL-encrypted connections. Fossil can be run directly from
104 stunnel in a mannar similar to inetd and xinetd. This can be used to provide
105 a secure link to a Fossil project. The configuration needed to get stunnel4
106 to invoke Fossil is very similar to the inetd and xinetd examples shown above.
107 See the stunnel4 documentation for details.
 
 
 
 
 
 
 
 
 
 
 
 
108 <p>
109 Using inetd or xinetd or stunnel is a more complex setup
110 than the "standalone" server, but it has the
111 advantage of only using system resources when an actual connection is
112 attempted. If no-one ever connects to that port, a Fossil server will
113
--- www/server.wiki
+++ www/server.wiki
@@ -102,11 +102,23 @@
102 [http://www.stunnel.org/ | Stunnel version 4] is an inetd-like process that
103 accepts and decodes SSL-encrypted connections. Fossil can be run directly from
104 stunnel in a mannar similar to inetd and xinetd. This can be used to provide
105 a secure link to a Fossil project. The configuration needed to get stunnel4
106 to invoke Fossil is very similar to the inetd and xinetd examples shown above.
107 The relevant parts of an stunnel configuration might look something
108 like the following:
109 <blockquote><pre><nowiki>
110 [https]
111 accept = www.ubercool-project.org:443
112 TIMEOUTclose = 0
113 exec = /usr/bin/fossil
114 execargs = /usr/bin/fossil http /home/fossil/ubercool.fossil --https
115 </nowiki></pre></blockquote>
116 See the stunnel4 documentation for further details bout the /etc/stunnel/stunnel.conf
117 configuration file. Note that the [fossil http] command should include the --https
118 option to let Fossil know to use "https" instead of "http" as the scheme on generated
119 hyperlinks.
120 <p>
121 Using inetd or xinetd or stunnel is a more complex setup
122 than the "standalone" server, but it has the
123 advantage of only using system resources when an actual connection is
124 attempted. If no-one ever connects to that port, a Fossil server will
125

Keyboard Shortcuts

Open search /
Next entry (timeline) j
Previous entry (timeline) k
Open focused entry Enter
Show this help ?
Toggle theme Top nav button