Fossil SCM

New documentation hyperlinks.

drh 2021-07-07 12:20 trunk
Commit 71499f138612c096019a5978a9533123433a77d37f0042f1af1aaa5bad1471e2
--- www/embeddeddoc.wiki
+++ www/embeddeddoc.wiki
@@ -207,11 +207,11 @@
207207
208208
The first part of this path, the "[http://fossil-scm.org/home]",
209209
is the base URL. You might have originally typed:
210210
[http://fossil-scm.org/]. The web server at the fossil-scm.org
211211
site automatically redirects such links by appending "home". The
212
-"home" file on fossil-scm.org is really a CGI script
212
+"home" file on fossil-scm.org is really a [./server/any/cgi.md|CGI script]
213213
which runs the fossil web service in CGI mode.
214214
The "home" CGI script looks like this:
215215
216216
<blockquote><pre>
217217
#!/usr/bin/fossil
218218
--- www/embeddeddoc.wiki
+++ www/embeddeddoc.wiki
@@ -207,11 +207,11 @@
207
208 The first part of this path, the "[http://fossil-scm.org/home]",
209 is the base URL. You might have originally typed:
210 [http://fossil-scm.org/]. The web server at the fossil-scm.org
211 site automatically redirects such links by appending "home". The
212 "home" file on fossil-scm.org is really a CGI script
213 which runs the fossil web service in CGI mode.
214 The "home" CGI script looks like this:
215
216 <blockquote><pre>
217 #!/usr/bin/fossil
218
--- www/embeddeddoc.wiki
+++ www/embeddeddoc.wiki
@@ -207,11 +207,11 @@
207
208 The first part of this path, the "[http://fossil-scm.org/home]",
209 is the base URL. You might have originally typed:
210 [http://fossil-scm.org/]. The web server at the fossil-scm.org
211 site automatically redirects such links by appending "home". The
212 "home" file on fossil-scm.org is really a [./server/any/cgi.md|CGI script]
213 which runs the fossil web service in CGI mode.
214 The "home" CGI script looks like this:
215
216 <blockquote><pre>
217 #!/usr/bin/fossil
218
--- www/selfhost.wiki
+++ www/selfhost.wiki
@@ -60,14 +60,14 @@
6060
onto a $5/month "droplet" [https://en.wikipedia.org/wiki/Virtual_private_server|VPS]
6161
from [https://www.digitalocean.com|Digital Ocean]
6262
located in San Francisco.
6363
6464
Server (3) is synchronized with the canonical server (1) by running
65
-the following command via cron:
65
+a command similar to the following via cron:
6666
6767
<blockquote><pre>
68
-/home/hwaci/bin/fossil sync -R /home/hwaci/fossil/fossil.fossil
68
+/usr/local/bin/fossil all sync -u
6969
</pre></blockquote>
7070
7171
Server (2) is a
7272
<a href="http://www.linode.com/">Linode 4096</a> located in Newark, NJ
7373
and set up just like the canonical server (1) with the addition of a
7474
--- www/selfhost.wiki
+++ www/selfhost.wiki
@@ -60,14 +60,14 @@
60 onto a $5/month "droplet" [https://en.wikipedia.org/wiki/Virtual_private_server|VPS]
61 from [https://www.digitalocean.com|Digital Ocean]
62 located in San Francisco.
63
64 Server (3) is synchronized with the canonical server (1) by running
65 the following command via cron:
66
67 <blockquote><pre>
68 /home/hwaci/bin/fossil sync -R /home/hwaci/fossil/fossil.fossil
69 </pre></blockquote>
70
71 Server (2) is a
72 <a href="http://www.linode.com/">Linode 4096</a> located in Newark, NJ
73 and set up just like the canonical server (1) with the addition of a
74
--- www/selfhost.wiki
+++ www/selfhost.wiki
@@ -60,14 +60,14 @@
60 onto a $5/month "droplet" [https://en.wikipedia.org/wiki/Virtual_private_server|VPS]
61 from [https://www.digitalocean.com|Digital Ocean]
62 located in San Francisco.
63
64 Server (3) is synchronized with the canonical server (1) by running
65 a command similar to the following via cron:
66
67 <blockquote><pre>
68 /usr/local/bin/fossil all sync -u
69 </pre></blockquote>
70
71 Server (2) is a
72 <a href="http://www.linode.com/">Linode 4096</a> located in Newark, NJ
73 and set up just like the canonical server (1) with the addition of a
74
--- www/serverext.wiki
+++ www/serverext.wiki
@@ -4,12 +4,12 @@
44
55
If you have a [./server/|Fossil server] for your project,
66
you can add [./aboutcgi.wiki|CGI]
77
extensions to that server. These extensions work like
88
any other CGI program, except that they also have access to the Fossil
9
-login information and can (optionally) leverage the "skins" of Fossil
10
-so that they appear to be more tightly integrated into the project.
9
+login information and can (optionally) leverage the "[./customskin.md|skins]"
10
+of Fossil so that they appear to be more tightly integrated into the project.
1111
1212
An example of where this is useful is the
1313
[https://sqlite.org/src/ext/checklist|checklist application] on
1414
the [https://sqlite.org/|SQLite] project. The checklist
1515
helps the SQLite developers track which release tests have passed,
@@ -25,11 +25,12 @@
2525
2626
<h2>2.0 How It Works</h2>
2727
2828
CGI Extensions are disabled by default.
2929
An administrator activates the CGI extension mechanism by specifying
30
-an "Extension Root Directory" or "extroot" as part of the server setup.
30
+an "Extension Root Directory" or "extroot" as part of the
31
+[./server/index.html|server setup].
3132
If the Fossil server is itself run as
3233
[./server/any/cgi.md|CGI], then add a line to the
3334
[./cgi.wiki#extroot|CGI script file] that says:
3435
3536
<blockquote><pre>
3637
--- www/serverext.wiki
+++ www/serverext.wiki
@@ -4,12 +4,12 @@
4
5 If you have a [./server/|Fossil server] for your project,
6 you can add [./aboutcgi.wiki|CGI]
7 extensions to that server. These extensions work like
8 any other CGI program, except that they also have access to the Fossil
9 login information and can (optionally) leverage the "skins" of Fossil
10 so that they appear to be more tightly integrated into the project.
11
12 An example of where this is useful is the
13 [https://sqlite.org/src/ext/checklist|checklist application] on
14 the [https://sqlite.org/|SQLite] project. The checklist
15 helps the SQLite developers track which release tests have passed,
@@ -25,11 +25,12 @@
25
26 <h2>2.0 How It Works</h2>
27
28 CGI Extensions are disabled by default.
29 An administrator activates the CGI extension mechanism by specifying
30 an "Extension Root Directory" or "extroot" as part of the server setup.
 
31 If the Fossil server is itself run as
32 [./server/any/cgi.md|CGI], then add a line to the
33 [./cgi.wiki#extroot|CGI script file] that says:
34
35 <blockquote><pre>
36
--- www/serverext.wiki
+++ www/serverext.wiki
@@ -4,12 +4,12 @@
4
5 If you have a [./server/|Fossil server] for your project,
6 you can add [./aboutcgi.wiki|CGI]
7 extensions to that server. These extensions work like
8 any other CGI program, except that they also have access to the Fossil
9 login information and can (optionally) leverage the "[./customskin.md|skins]"
10 of Fossil so that they appear to be more tightly integrated into the project.
11
12 An example of where this is useful is the
13 [https://sqlite.org/src/ext/checklist|checklist application] on
14 the [https://sqlite.org/|SQLite] project. The checklist
15 helps the SQLite developers track which release tests have passed,
@@ -25,11 +25,12 @@
25
26 <h2>2.0 How It Works</h2>
27
28 CGI Extensions are disabled by default.
29 An administrator activates the CGI extension mechanism by specifying
30 an "Extension Root Directory" or "extroot" as part of the
31 [./server/index.html|server setup].
32 If the Fossil server is itself run as
33 [./server/any/cgi.md|CGI], then add a line to the
34 [./cgi.wiki#extroot|CGI script file] that says:
35
36 <blockquote><pre>
37

Keyboard Shortcuts

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