Fossil SCM

New documentation on how CGI works in Fossil. This is a work-in-progress.

drh 2016-08-02 19:42 trunk

Commit c55f54d0fcfaf2781ec66a06a1ffb3113ac1cefd

Parent c14ecc432af739b…

4 files changed +124 +1 +3 +3 -1

+ www/aboutcgi.wiki ~ www/mkindex.tcl ~ www/permutedindex.html ~ www/server.wiki

A www/aboutcgi.wiki

+124

		--- a/www/aboutcgi.wiki
		+++ b/www/aboutcgi.wiki
		@@ -0,0 +1,124 @@
	1	+<title>How C<h2>Introduction</h2><blockquote>le>
	2	+
	3	+<h2>Introduction</h2>
	4	+
	5	+<p>CGI or "Common Gateway Interface" is a venerable yet reliable technique for
	6	+generating dynamic web content. This article give a quick background on how
	7	+CGI works and describes how Fossil can act as a CGI service.
	8	+<p>This is a "how it works" guide. If you just want to set up Fossil
	9	+as a CGI server, see the [./server.wiki \| Fossil Server Setup] page.eview Of CGI</h2>
	10	+
	11	+An HTTP<blockquote R<p>request is a block of text that is sent by a client application
	12	+(usually a web browser) and arrives at the web server over a network
	13	+connection. The HTTP request contains a URL that describes the information
	14	+being requested. The URL in the HTTP request is typically the same URL
	15	+that appears in the URL bar at the top of the web bra "?" character followed by
	16	+query parameters. The HTTP will usually also contain other information
	17	+such as the name of the application that made the request, whether or
	18	+not the requesting application can accept a compressed reply, POST
	19	+parameters from forms, and so fexver is to interpret the HTTP request and<p>erpret the HTTP request and formulate
	20	+an appropriate reply.
	21	+The web server is free to interpret the_HTTP .
	22	+Buest in any way it_HTTP request in any way it wants,
	23	+but most web servers fwww.fossil-scm.org/fossile: details may vary from one web server to another.)
	24	+
	25	+Suppose <p>he URL in the HTTP request looks lURL inppropriate reply.
	26	+search tb></blockquote> servers will search their content area for files that match
	27	+some prefix of the URL. The search starts with <b>/one</b>, then goes to
	28	+<b>/one/two</b>, then <b>/one/two/timeline</b>, and finally
	29	+<b>/one/two/timeline/f
	30	+at describchecked. The search stops at the first
	31	+match.
	32	+
	33	+Suppose the first match is <b>/one/<p>two</b>. If <b>/one/two</b> is an
	34	+ordinary file in the content area, then that file is returned as static
	35	+content. The "<b>/timeline/four</b>" suffix is silently ignored.
	36	+
	37	+If <b>/one/two</b> is a CGI script <p>
	38	+e/two</b> is an
	39	+ordinar<title>How C<h2>Introduction</h2><blockquote>le>
	40	+
	41	+<h2>Introduction</h2>
	42	+
	43	+CGI or "Common Gateway Interface" is a venerable yet reliable tech2>It application
	44	+(usually a web browser) and arrives at the web server over a network
	45	+connection. The HTTP request contains a URL that describes the information
	46	+being requested. The URL in the HTTP request is typically the same URL
	47	+that appears in the URL bar at the top of the web bra "?" character followed by
	48	+query parameters. The HTTP will usually also contain other information
	49	+such as the name of the application that made the request, whether or
	50	+not the requesting application can accept a compressed reply, POS uested. The URL in the HTTP request is typically the same URL
	51	+that appears in the URL bar at the top of the web bra "?" character followed by
	52	+query parameters. The HTTP will usually also contain other information
	53	+such as the name of the application that made the request, whether or
	54	+not the requesting application can accept a compressed forms, and so fexver is to interpret the HTTP request and<p>erpret the HTTP request and formulate
	55	+an appropriate reply.
	56	+The web server is free to interpret the_HTTP .
	57	+Buest in any way it_HTTP request in any way it wants,
	58	+but most web servers fwww.fossil-scm.org/fossile: details may vary from one web server to another.)
	59	+
	60	+Suppose <p>he URL in the HTTP request looks lURL inppropriate reply.
	61	+search tb></blockquote> servers will search their content area for files that m r "Common Gateway Interface" is a venerable yet reliable technique for
	62	+generating dynamic web content. This article gives a quick background on how
	63	+CGI works and describes how Fossil can act as a CGI service.
	64	+<p>This is a "how it works" guide. If you just want to set up Fo<<b>/one/<p>two</b>. If <b>/one/two</b> is an
	65	+ordinary file in the content area, then that file is returned as static
	66	+content. The "<b>/timeline/four</b>" suffix is silently ignored.
	67	+
	68	+If <b>/one/two</b> is a CGI script <p>
	69	+e/two</b> is an
	70	+ordinar<title>How C<h2>Introduction</h2><blockquote>le>
	71	+
	72	+<h2>Introduction</h2>
	73	+
	74	+CGI or "Common Gateway Interface" is a venerable yet reliable tech2>It application
	75	+(usually a web browser) and arrives at the web server over a network
	76	+connection. The HTTP request contains a URL that describes the information
	77	+being requested. The URL in the HTTP request is typically the same URL
	78	+that appears in the URL bar at the top of the web kra "?" character followed by
	79	+query parameters. The HTTP will usually also contain other information
	80	+such as the name of the application that made the request, whether or
	81	+not the requesting application can accept a compressed reply, POST
	82	+parameters from forms, and so forth.
	83	+
	84	+The job of the web server is to interpret the so fexver is to interpret the HTTP request arpret the HTTP request and formulate
	85	+an appropriate reply.
	86	+The web server is free to interpret the_HTTP .
	87	+Buest in any way it_HTTP request in any way it wants,
	88	+but most web servers fwww.fossil-scm.org/fossile: details may vary from one web server to another.)
	89	+
	90	+Suppose <p>he URL in the HTTP request looks lURL inppropriate reply.
	91	+search tb></blockquote> servers will search their content area for files that match
	92	+some prefix of the URL. The search starts with <b>/one</b>, then goes to
	93	+<b>/one/two</b>, then <br>/one/two/timeline</b>, and finally
	94	+<b>/one/two/timeline/four</b> is checked. The search stops at the first
	95	+match.
	96	+
	97	+Suppose the first match is <b>/one/<p>two</b>. If <b>/one/two</b> is an
	98	+ordinary file in the content area, then that file is returned as static
	99	+content. The "<b>/timeline/four</b>" suffix is silently ignored.
	100	+
	101	+If <b>/one/two</b> is a CGI script <p>
	102	+e/two</b> is an
	103	+ordinar<title>How C<h2>Introduction</h2><blockquote>le>
	104	+
	105	+<h2>Introduction</h2>
	106	+
	107	+CGI or "Common Gateway Interface" is a venerable yet reliable tech2>It application
	108	+(usually a web browser) and arrives at the web server over a network
	109	+connection. The HTTP request contains a URL that describsTP request is typically the same URL
	110	+that appears in the URL bar at the top of the web bra "?" character followed by
	111	+query parameters. Thyourstuff.comr or
	112	+not the rech as the name of the application that made the reques t, whether or
	113	+not the requesting application can accept a compressed reply, POST
	114	+parameters from forms, and so forth.
	115	+
	116	+The job of the web server is to interpret the HTTP request andwww.fossil-scm.org/fossil
	117	+Many Fossil servers implementwww.fossil-scm.org/fossil/three?abc=xyz\|test-env]
	118	+webpage that shows some of the CGI environment
	119	+variables that Fossil pays attention to.
	120	+
	121	+In addition to setting various CGI environment variables, if the HTTP
	122	+request conta<p>, if the HTTP
	123	+request contains POST content, then the web server relays the POST content
	124	+to standard input of the CGI s

	--- a/www/aboutcgi.wiki
	+++ b/www/aboutcgi.wiki
	@@ -0,0 +1,124 @@

	--- a/www/aboutcgi.wiki
	+++ b/www/aboutcgi.wiki
	@@ -0,0 +1,124 @@
1	<title>How C<h2>Introduction</h2><blockquote>le>
2
3	<h2>Introduction</h2>
4
5	<p>CGI or "Common Gateway Interface" is a venerable yet reliable technique for
6	generating dynamic web content. This article give a quick background on how
7	CGI works and describes how Fossil can act as a CGI service.
8	<p>This is a "how it works" guide. If you just want to set up Fossil
9	as a CGI server, see the [./server.wiki \| Fossil Server Setup] page.eview Of CGI</h2>
10
11	An HTTP<blockquote R<p>request is a block of text that is sent by a client application
12	(usually a web browser) and arrives at the web server over a network
13	connection. The HTTP request contains a URL that describes the information
14	being requested. The URL in the HTTP request is typically the same URL
15	that appears in the URL bar at the top of the web bra "?" character followed by
16	query parameters. The HTTP will usually also contain other information
17	such as the name of the application that made the request, whether or
18	not the requesting application can accept a compressed reply, POST
19	parameters from forms, and so fexver is to interpret the HTTP request and<p>erpret the HTTP request and formulate
20	an appropriate reply.
21	The web server is free to interpret the_HTTP .
22	Buest in any way it_HTTP request in any way it wants,
23	but most web servers fwww.fossil-scm.org/fossile: details may vary from one web server to another.)
24
25	Suppose <p>he URL in the HTTP request looks lURL inppropriate reply.
26	search tb></blockquote> servers will search their content area for files that match
27	some prefix of the URL. The search starts with <b>/one</b>, then goes to
28	<b>/one/two</b>, then <b>/one/two/timeline</b>, and finally
29	<b>/one/two/timeline/f
30	at describchecked. The search stops at the first
31	match.
32
33	Suppose the first match is <b>/one/<p>two</b>. If <b>/one/two</b> is an
34	ordinary file in the content area, then that file is returned as static
35	content. The "<b>/timeline/four</b>" suffix is silently ignored.
36
37	If <b>/one/two</b> is a CGI script <p>
38	e/two</b> is an
39	ordinar<title>How C<h2>Introduction</h2><blockquote>le>
40
41	<h2>Introduction</h2>
42
43	CGI or "Common Gateway Interface" is a venerable yet reliable tech2>It application
44	(usually a web browser) and arrives at the web server over a network
45	connection. The HTTP request contains a URL that describes the information
46	being requested. The URL in the HTTP request is typically the same URL
47	that appears in the URL bar at the top of the web bra "?" character followed by
48	query parameters. The HTTP will usually also contain other information
49	such as the name of the application that made the request, whether or
50	not the requesting application can accept a compressed reply, POS uested. The URL in the HTTP request is typically the same URL
51	that appears in the URL bar at the top of the web bra "?" character followed by
52	query parameters. The HTTP will usually also contain other information
53	such as the name of the application that made the request, whether or
54	not the requesting application can accept a compressed forms, and so fexver is to interpret the HTTP request and<p>erpret the HTTP request and formulate
55	an appropriate reply.
56	The web server is free to interpret the_HTTP .
57	Buest in any way it_HTTP request in any way it wants,
58	but most web servers fwww.fossil-scm.org/fossile: details may vary from one web server to another.)
59
60	Suppose <p>he URL in the HTTP request looks lURL inppropriate reply.
61	search tb></blockquote> servers will search their content area for files that m r "Common Gateway Interface" is a venerable yet reliable technique for
62	generating dynamic web content. This article gives a quick background on how
63	CGI works and describes how Fossil can act as a CGI service.
64	<p>This is a "how it works" guide. If you just want to set up Fo<<b>/one/<p>two</b>. If <b>/one/two</b> is an
65	ordinary file in the content area, then that file is returned as static
66	content. The "<b>/timeline/four</b>" suffix is silently ignored.
67
68	If <b>/one/two</b> is a CGI script <p>
69	e/two</b> is an
70	ordinar<title>How C<h2>Introduction</h2><blockquote>le>
71
72	<h2>Introduction</h2>
73
74	CGI or "Common Gateway Interface" is a venerable yet reliable tech2>It application
75	(usually a web browser) and arrives at the web server over a network
76	connection. The HTTP request contains a URL that describes the information
77	being requested. The URL in the HTTP request is typically the same URL
78	that appears in the URL bar at the top of the web kra "?" character followed by
79	query parameters. The HTTP will usually also contain other information
80	such as the name of the application that made the request, whether or
81	not the requesting application can accept a compressed reply, POST
82	parameters from forms, and so forth.
83
84	The job of the web server is to interpret the so fexver is to interpret the HTTP request arpret the HTTP request and formulate
85	an appropriate reply.
86	The web server is free to interpret the_HTTP .
87	Buest in any way it_HTTP request in any way it wants,
88	but most web servers fwww.fossil-scm.org/fossile: details may vary from one web server to another.)
89
90	Suppose <p>he URL in the HTTP request looks lURL inppropriate reply.
91	search tb></blockquote> servers will search their content area for files that match
92	some prefix of the URL. The search starts with <b>/one</b>, then goes to
93	<b>/one/two</b>, then <br>/one/two/timeline</b>, and finally
94	<b>/one/two/timeline/four</b> is checked. The search stops at the first
95	match.
96
97	Suppose the first match is <b>/one/<p>two</b>. If <b>/one/two</b> is an
98	ordinary file in the content area, then that file is returned as static
99	content. The "<b>/timeline/four</b>" suffix is silently ignored.
100
101	If <b>/one/two</b> is a CGI script <p>
102	e/two</b> is an
103	ordinar<title>How C<h2>Introduction</h2><blockquote>le>
104
105	<h2>Introduction</h2>
106
107	CGI or "Common Gateway Interface" is a venerable yet reliable tech2>It application
108	(usually a web browser) and arrives at the web server over a network
109	connection. The HTTP request contains a URL that describsTP request is typically the same URL
110	that appears in the URL bar at the top of the web bra "?" character followed by
111	query parameters. Thyourstuff.comr or
112	not the rech as the name of the application that made the reques t, whether or
113	not the requesting application can accept a compressed reply, POST
114	parameters from forms, and so forth.
115
116	The job of the web server is to interpret the HTTP request andwww.fossil-scm.org/fossil
117	Many Fossil servers implementwww.fossil-scm.org/fossil/three?abc=xyz\|test-env]
118	webpage that shows some of the CGI environment
119	variables that Fossil pays attention to.
120
121	In addition to setting various CGI environment variables, if the HTTP
122	request conta<p>, if the HTTP
123	request contains POST content, then the web server relays the POST content
124	to standard input of the CGI s

M www/mkindex.tcl

		--- www/mkindex.tcl
		+++ www/mkindex.tcl
		@@ -5,10 +5,11 @@
5	5	#
6	6	# tclsh mkindex.tcl
7	7	#
8	8
9	9	set doclist {
	10	+ aboutcgi.wiki {How CGI Works In Fossil}
10	11	adding_code.wiki {Adding New Features To Fossil}
11	12	adding_code.wiki {Hacking Fossil}
12	13	antibot.wiki {Defense against Spiders and Bots}
13	14	blame.wiki {The Annotate/Blame Algorithm Of Fossil}
14	15	branching.wiki {Branching, Forking, Merging, and Tagging}
15	16

	--- www/mkindex.tcl
	+++ www/mkindex.tcl
	@@ -5,10 +5,11 @@
5	#
6	# tclsh mkindex.tcl
7	#
8
9	set doclist {

10	adding_code.wiki {Adding New Features To Fossil}
11	adding_code.wiki {Hacking Fossil}
12	antibot.wiki {Defense against Spiders and Bots}
13	blame.wiki {The Annotate/Blame Algorithm Of Fossil}
14	branching.wiki {Branching, Forking, Merging, and Tagging}
15

	--- www/mkindex.tcl
	+++ www/mkindex.tcl
	@@ -5,10 +5,11 @@
5	#
6	# tclsh mkindex.tcl
7	#
8
9	set doclist {
10	aboutcgi.wiki {How CGI Works In Fossil}
11	adding_code.wiki {Adding New Features To Fossil}
12	adding_code.wiki {Hacking Fossil}
13	antibot.wiki {Defense against Spiders and Bots}
14	blame.wiki {The Annotate/Blame Algorithm Of Fossil}
15	branching.wiki {Branching, Forking, Merging, and Tagging}
16

M www/permutedindex.html

		--- www/permutedindex.html
		+++ www/permutedindex.html
		@@ -35,10 +35,11 @@
35	35	<li><a href="antibot.wiki">Bots — Defense against Spiders and</a></li>
36	36	<li><a href="private.wiki">Branches — Creating, Syncing, and Deleting Private</a></li>
37	37	<li><a href="branching.wiki">Branching, Forking, Merging, and Tagging</a></li>
38	38	<li><a href="bugtheory.wiki">Bug Tracking In Fossil</a></li>
39	39	<li><a href="makefile.wiki">Build Process — The Fossil</a></li>
	40	+<li><a href="aboutcgi.wiki">CGI Works In Fossil — How</a></li>
40	41	<li><a href="changes.wiki">Changelog — Fossil</a></li>
41	42	<li><a href="checkin_names.wiki">Check-in And Version Names</a></li>
42	43	<li><a href="checkin.wiki">Check-in Checklist</a></li>
43	44	<li><a href="checkin.wiki">Checklist — Check-in</a></li>
44	45	<li><a href="../test/release-checklist.wiki">Checklist — Pre-Release Testing</a></li>
		@@ -110,10 +111,11 @@
110	111	<li><a href="hacker-howto.wiki">Hacker How-To</a></li>
111	112	<li><a href="adding_code.wiki">Hacking Fossil</a></li>
112	113	<li><a href="hints.wiki">Hints — Fossil Tips And Usage</a></li>
113	114	<li><a href="index.wiki">Home Page</a></li>
114	115	<li><a href="selfhost.wiki">Hosting Repositories — Fossil Self</a></li>
	116	+<li><a href="aboutcgi.wiki">How CGI Works In Fossil</a></li>
115	117	<li><a href="server.wiki">How To Configure A Fossil Server</a></li>
116	118	<li><a href="newrepo.wiki">How To Create A New Fossil Repository</a></li>
117	119	<li><a href="encryptedrepos.wiki">How To Use Encrypted Repositories</a></li>
118	120	<li><a href="hacker-howto.wiki">How-To — Hacker</a></li>
119	121	<li><a href="fossil-from-msvc.wiki">IDE — Integrating Fossil in the Microsoft Express 2010</a></li>
		@@ -209,6 +211,7 @@
209	211	<li><a href="customskin.md">Web Pages — Theming: Customizing The Appearance of</a></li>
210	212	<li><a href="webpage-ex.md">Webpage Examples</a></li>
211	213	<li><a href="quotes.wiki">What People Are Saying About Fossil, Git, and DVCSes in General — Quotes:</a></li>
212	214	<li><a href="wikitheory.wiki">Wiki In Fossil</a></li>
213	215	<li><a href="ssl.wiki">with Fossil — Using SSL</a></li>
	216	+<li><a href="aboutcgi.wiki">Works In Fossil — How CGI</a></li>
214	217	</ul></div>
215	218

	--- www/permutedindex.html
	+++ www/permutedindex.html
	@@ -35,10 +35,11 @@
35	<li><a href="antibot.wiki">Bots — Defense against Spiders and</a></li>
36	<li><a href="private.wiki">Branches — Creating, Syncing, and Deleting Private</a></li>
37	<li><a href="branching.wiki">Branching, Forking, Merging, and Tagging</a></li>
38	<li><a href="bugtheory.wiki">Bug Tracking In Fossil</a></li>
39	<li><a href="makefile.wiki">Build Process — The Fossil</a></li>

40	<li><a href="changes.wiki">Changelog — Fossil</a></li>
41	<li><a href="checkin_names.wiki">Check-in And Version Names</a></li>
42	<li><a href="checkin.wiki">Check-in Checklist</a></li>
43	<li><a href="checkin.wiki">Checklist — Check-in</a></li>
44	<li><a href="../test/release-checklist.wiki">Checklist — Pre-Release Testing</a></li>
	@@ -110,10 +111,11 @@
110	<li><a href="hacker-howto.wiki">Hacker How-To</a></li>
111	<li><a href="adding_code.wiki">Hacking Fossil</a></li>
112	<li><a href="hints.wiki">Hints — Fossil Tips And Usage</a></li>
113	<li><a href="index.wiki">Home Page</a></li>
114	<li><a href="selfhost.wiki">Hosting Repositories — Fossil Self</a></li>

115	<li><a href="server.wiki">How To Configure A Fossil Server</a></li>
116	<li><a href="newrepo.wiki">How To Create A New Fossil Repository</a></li>
117	<li><a href="encryptedrepos.wiki">How To Use Encrypted Repositories</a></li>
118	<li><a href="hacker-howto.wiki">How-To — Hacker</a></li>
119	<li><a href="fossil-from-msvc.wiki">IDE — Integrating Fossil in the Microsoft Express 2010</a></li>
	@@ -209,6 +211,7 @@
209	<li><a href="customskin.md">Web Pages — Theming: Customizing The Appearance of</a></li>
210	<li><a href="webpage-ex.md">Webpage Examples</a></li>
211	<li><a href="quotes.wiki">What People Are Saying About Fossil, Git, and DVCSes in General — Quotes:</a></li>
212	<li><a href="wikitheory.wiki">Wiki In Fossil</a></li>
213	<li><a href="ssl.wiki">with Fossil — Using SSL</a></li>

214	</ul></div>
215

	--- www/permutedindex.html
	+++ www/permutedindex.html
	@@ -35,10 +35,11 @@
35	<li><a href="antibot.wiki">Bots — Defense against Spiders and</a></li>
36	<li><a href="private.wiki">Branches — Creating, Syncing, and Deleting Private</a></li>
37	<li><a href="branching.wiki">Branching, Forking, Merging, and Tagging</a></li>
38	<li><a href="bugtheory.wiki">Bug Tracking In Fossil</a></li>
39	<li><a href="makefile.wiki">Build Process — The Fossil</a></li>
40	<li><a href="aboutcgi.wiki">CGI Works In Fossil — How</a></li>
41	<li><a href="changes.wiki">Changelog — Fossil</a></li>
42	<li><a href="checkin_names.wiki">Check-in And Version Names</a></li>
43	<li><a href="checkin.wiki">Check-in Checklist</a></li>
44	<li><a href="checkin.wiki">Checklist — Check-in</a></li>
45	<li><a href="../test/release-checklist.wiki">Checklist — Pre-Release Testing</a></li>
	@@ -110,10 +111,11 @@
111	<li><a href="hacker-howto.wiki">Hacker How-To</a></li>
112	<li><a href="adding_code.wiki">Hacking Fossil</a></li>
113	<li><a href="hints.wiki">Hints — Fossil Tips And Usage</a></li>
114	<li><a href="index.wiki">Home Page</a></li>
115	<li><a href="selfhost.wiki">Hosting Repositories — Fossil Self</a></li>
116	<li><a href="aboutcgi.wiki">How CGI Works In Fossil</a></li>
117	<li><a href="server.wiki">How To Configure A Fossil Server</a></li>
118	<li><a href="newrepo.wiki">How To Create A New Fossil Repository</a></li>
119	<li><a href="encryptedrepos.wiki">How To Use Encrypted Repositories</a></li>
120	<li><a href="hacker-howto.wiki">How-To — Hacker</a></li>
121	<li><a href="fossil-from-msvc.wiki">IDE — Integrating Fossil in the Microsoft Express 2010</a></li>
	@@ -209,6 +211,7 @@
211	<li><a href="customskin.md">Web Pages — Theming: Customizing The Appearance of</a></li>
212	<li><a href="webpage-ex.md">Webpage Examples</a></li>
213	<li><a href="quotes.wiki">What People Are Saying About Fossil, Git, and DVCSes in General — Quotes:</a></li>
214	<li><a href="wikitheory.wiki">Wiki In Fossil</a></li>
215	<li><a href="ssl.wiki">with Fossil — Using SSL</a></li>
216	<li><a href="aboutcgi.wiki">Works In Fossil — How CGI</a></li>
217	</ul></div>
218

M www/server.wiki

+3 -1

		--- www/server.wiki
		+++ www/server.wiki
		@@ -5,11 +5,13 @@
5	5	For example, the complete [https://www.fossil-scm.org/] website, including the
6	6	page you are now reading (but excepting the
7	7	[https://www.fossil-scm.org/download.html\|download page]),
8	8	is just a Fossil server displaying the content of the
9	9	self-hosting repository for Fossil.</p>
10		-<p>This article is a guide for setting up your own Fossil server.</p></blockquote>
	10	+<p>This article is a guide for setting up your own Fossil server.
	11	+<p>See the [./aboutcgi.wiki\|How CGI Works In Fossil] document for background
	12	+information on the underlying technology.</p></blockquote>
11	13	<h2>Overview</h2><blockquote>
12	14	There are basically four ways to set up a Fossil server:
13	15	<ol>
14	16	<li>A stand-alone server
15	17	<li>Using inetd or xinetd or stunnel
16	18

	--- www/server.wiki
	+++ www/server.wiki
	@@ -5,11 +5,13 @@
5	For example, the complete [https://www.fossil-scm.org/] website, including the
6	page you are now reading (but excepting the
7	[https://www.fossil-scm.org/download.html\|download page]),
8	is just a Fossil server displaying the content of the
9	self-hosting repository for Fossil.</p>
10	<p>This article is a guide for setting up your own Fossil server.</p></blockquote>


11	<h2>Overview</h2><blockquote>
12	There are basically four ways to set up a Fossil server:
13	<ol>
14	<li>A stand-alone server
15	<li>Using inetd or xinetd or stunnel
16

	--- www/server.wiki
	+++ www/server.wiki
	@@ -5,11 +5,13 @@
5	For example, the complete [https://www.fossil-scm.org/] website, including the
6	page you are now reading (but excepting the
7	[https://www.fossil-scm.org/download.html\|download page]),
8	is just a Fossil server displaying the content of the
9	self-hosting repository for Fossil.</p>
10	<p>This article is a guide for setting up your own Fossil server.
11	<p>See the [./aboutcgi.wiki\|How CGI Works In Fossil] document for background
12	information on the underlying technology.</p></blockquote>
13	<h2>Overview</h2><blockquote>
14	There are basically four ways to set up a Fossil server:
15	<ol>
16	<li>A stand-alone server
17	<li>Using inetd or xinetd or stunnel
18

Fossil SCM

Keyboard Shortcuts