Fossil SCM

Added www/capabilities.md, a complete treatment on user capabilities, user categories, login groups, and administration matters involving all of this. It does not replace the pre-existing admin-v-setup.md doc, but a bit of its content did move into this new doc. The new doc also contains the user capability info previously in the forum.wiki doc. This is on a branch because although it's quite useful already, it could use some work before being merged down. At the barest minimum, there are some unanswered questions in the new doc that need addressing. This new doc does not replace the existing documentation in the UI. It may be that we end up paring that down a bit now that we have a full doc to refer to, but that is a topic for the forum thread that will appear shortly after this checkin.

wyoung 2019-08-23 08:31 trunk
Commit 832f107ebbb4a82dc71a44d2b6a073e5306c41b6e1dfa5484549627723a2fb58
Parent 9fcd6e443cdefb5…
4 files changed +9 -11 +132 +4 -28 +1
~ www/admin-v-setup.md + www/capabilities.md ~ www/forum.wiki ~ www/mkindex.tcl
M www/admin-v-setup.md
+9 -11
--- www/admin-v-setup.md
+++ www/admin-v-setup.md
@@ -1,21 +1,18 @@
11
 # The Differences Between the Setup and Admin User Capabilities
22
3
-Several of the Fossil user capabilities form a clear power hierarchy.
4
-Mathematically speaking:
5
-
6
-> *Setup > Admin > Moderator > User > Subscriber > Anonymous > Nobody*
7
-
8
-This document explains the distinction between the first two. For the
9
-others, see:
10
-
3
+This document explains the distinction between [Setup users][su] and
4
+[Admin users][au]. For other information about use types, see:
5
+
6
+* [Administering User Capabilities](./capabilities.md)
117
 * [How Moderation Works](./forum.wiki#moderation)
12
-
138
 * [Users vs Subscribers](./alerts.md#uvs)
14
-
159
 * [Defense Against Spiders](./antibot.wiki)
1610
11
+[au]: ./capabilities.md#a
12
+[su]: ./capabilities.md#apsu
13
+
1714
1815
 ## Philosophical Core
1916
2017
 The Setup user "owns" the Fossil repository and may delegate a subset of
2118
 that power to one or more Admin users.
@@ -79,10 +76,12 @@
7976
 free to correct this without bothering the Setup user.
8077
8178
 Another common case is that the Setup user upgrades Fossil on the server
8279
 but forgets to merge the upstream skin changes: Admin users are
8380
 entrusted to do that work on behalf of the Setup user.
81
+
82
+[ucap]: ./capabilities.md#ref
8483
8584
8685
 ## Capability Groups
8786
8887
 We can break up the set of powers the Admin user capability grants into
@@ -321,6 +320,5 @@
321320
 [forum]: https://fossil-scm.org/forum/
322321
 [rs]: https://www.fossil-scm.org/index.html/doc/trunk/www/settings.wiki
323322
 [sia]: https://fossil-scm.org/fossil/artifact?udc=1&ln=1259-1260&name=0fda31b6683c206a
324323
 [th1]: https://www.fossil-scm.org/index.html/doc/trunk/www/th1.md
325324
 [tt]: https://en.wikipedia.org/wiki/Tiger_team#Security
326
-[ucap]: https://fossil-scm.org/fossil/setup_ucap_list
327325
328326
ADDED www/capabilities.md
--- www/admin-v-setup.md
+++ www/admin-v-setup.md
@@ -1,21 +1,18 @@
1 # The Differences Between the Setup and Admin User Capabilities
2
3 Several of the Fossil user capabilities form a clear power hierarchy.
4 Mathematically speaking:
5
6 > *Setup > Admin > Moderator > User > Subscriber > Anonymous > Nobody*
7
8 This document explains the distinction between the first two. For the
9 others, see:
10
11 * [How Moderation Works](./forum.wiki#moderation)
12
13 * [Users vs Subscribers](./alerts.md#uvs)
14
15 * [Defense Against Spiders](./antibot.wiki)
16
 
 
 
17
18 ## Philosophical Core
19
20 The Setup user "owns" the Fossil repository and may delegate a subset of
21 that power to one or more Admin users.
@@ -79,10 +76,12 @@
79 free to correct this without bothering the Setup user.
80
81 Another common case is that the Setup user upgrades Fossil on the server
82 but forgets to merge the upstream skin changes: Admin users are
83 entrusted to do that work on behalf of the Setup user.
 
 
84
85
86 ## Capability Groups
87
88 We can break up the set of powers the Admin user capability grants into
@@ -321,6 +320,5 @@
321 [forum]: https://fossil-scm.org/forum/
322 [rs]: https://www.fossil-scm.org/index.html/doc/trunk/www/settings.wiki
323 [sia]: https://fossil-scm.org/fossil/artifact?udc=1&ln=1259-1260&name=0fda31b6683c206a
324 [th1]: https://www.fossil-scm.org/index.html/doc/trunk/www/th1.md
325 [tt]: https://en.wikipedia.org/wiki/Tiger_team#Security
326 [ucap]: https://fossil-scm.org/fossil/setup_ucap_list
327
328 DDED www/capabilities.md
--- www/admin-v-setup.md
+++ www/admin-v-setup.md
@@ -1,21 +1,18 @@
1 # The Differences Between the Setup and Admin User Capabilities
2
3 This document explains the distinction between [Setup users][su] and
4 [Admin users][au]. For other information about use types, see:
5
6 * [Administering User Capabilities](./capabilities.md)
 
 
 
 
7 * [How Moderation Works](./forum.wiki#moderation)
 
8 * [Users vs Subscribers](./alerts.md#uvs)
 
9 * [Defense Against Spiders](./antibot.wiki)
10
11 [au]: ./capabilities.md#a
12 [su]: ./capabilities.md#apsu
13
14
15 ## Philosophical Core
16
17 The Setup user "owns" the Fossil repository and may delegate a subset of
18 that power to one or more Admin users.
@@ -79,10 +76,12 @@
76 free to correct this without bothering the Setup user.
77
78 Another common case is that the Setup user upgrades Fossil on the server
79 but forgets to merge the upstream skin changes: Admin users are
80 entrusted to do that work on behalf of the Setup user.
81
82 [ucap]: ./capabilities.md#ref
83
84
85 ## Capability Groups
86
87 We can break up the set of powers the Admin user capability grants into
@@ -321,6 +320,5 @@
320 [forum]: https://fossil-scm.org/forum/
321 [rs]: https://www.fossil-scm.org/index.html/doc/trunk/www/settings.wiki
322 [sia]: https://fossil-scm.org/fossil/artifact?udc=1&ln=1259-1260&name=0fda31b6683c206a
323 [th1]: https://www.fossil-scm.org/index.html/doc/trunk/www/th1.md
324 [tt]: https://en.wikipedia.org/wiki/Tiger_team#Security
 
325
326 DDED www/capabilities.md
A www/capabilities.md
+132
--- a/www/capabilities.md
+++ b/www/capabilities.md
@@ -0,0 +1,132 @@
1
+local fileadding a
2
+[**Se capability
3
+namenamenamenamenamenamenamenamenamenamecap].
4
+
5
+ The SSH client command defaults to “`ssh -e none -T`” on most
6
+ platforms except Windows where it defaults to “`plink -ssh -T`”.
7
+ Yssh-command`
8
+ setticap]: https://fossil-scm.org/home/fileabilitie?ci=8813ae91a699ac73&name=src%2Fm
9
+characters, one perations over
10
+`http[s]://` U
11
+ations over
12
+`http[s] diffeCheck data out from Fossil/home/fileabilitiloca the ability to “open” a local repo clone or
13
+ switch branches in that clone. It only controls whether similar
14
+ operations over HTTP to a remote repo areto viewfor example,
15
+ since that basicallyamounts to opening a file in the remote repo.
16
+ also controls th
17
+ and [`/raw`][ru] URLs.file’s user category set is currently fixed. There is no way to define
18
+custom categories.
19
+
20
+These categories form a strict hierarchy. Mathematically speaking:
21
+all of/fossil-scm.org/home/fileabilitie?ci=8813ae91a699ac73&name=src%2Fm
22
+characters, one perations over
23
+`http[s]://` U
24
+ations over
25
+`http[s] dilocal fileadding a
26
+[**Se capability
27
+namenamenamenamenamenamenamenamenamenamecap].
28
+
29
+ The SSH Mnemonic: check
30
+ **i**nl fileadding a
31
+[**Se capability
32
+namenamenamenamenamenamenamenamenamenamecap].
33
+
34
+ The SSH client command defaults to “`ssh -e none -T`�*Se capability
35
+namenamenameMnemonic:
36
+ ileabilitie?ci=8813ae91a699ac73&name=src%2Fm
37
+characters, one perations over
38
+`http[s]://` U
39
+ations over
40
+`http[s] diffeCheck data out from Fossillocal fileadding a
41
+[**Se capability
42
+namenamenamenamenamenamenamenamenamenamecap].
43
+
44
+ l fileadding a
45
+[**Se capability
46
+namenamenamenamenamenamenamenamenamenamecap].
47
+
48
+ Thcapability
49
+namenamenamenamenamenamenamenamenamenamecap].
50
+
51
+ The SSH client command defaults to “`ssh -e none -T`” on most
52
+ platforms except Windows where it defaults to “`plink -ssh -T`”.
53
+ Yssh-command`
54
+ setticap]: https://fossil-scm.org/home/fileabilitie?ci=8813ae91a699ac73&name=src%2Fm
55
+characters, one perations over
56
+`http[s]://` U
57
+ations over
58
+`http[s] diffeCheck data out from Fossil/home/fileabilitiloca the ability to “open” a local repo clone or
59
+ switch branches in that clone. It only controls whether similar
60
+ operations over HTTP to a remote repo aret..Mnemonic: **w**rite
61
+ local fileadding a
62
+[**Se capability
63
+namenamenamenamenamenamenamenamenamenamecap].
64
+
65
+ The SSH client command defaults to “`ssh -e none -T`” on most
66
+ platforms except Windows where it defaults to “`plink adding a
67
+[**Se capability
68
+namenamenamenamenamenamenamenamenamenamecap].
69
+
70
+ The SSH client command defaults to “`ssh -e none -T`” on most
71
+ platforms except Windows where it defaults to “`plink -ssh -T`”.
72
+ Yssh-command`
73
+ setticap]: https://fossil-scm.org/home/fileabilitie?ci=8813ae91a699ac73&name=src%2Fm
74
+characters, one perations over
75
+`http[s]://` U
76
+ations over
77
+`http[s] diffeCheck data out from Fossil/home/fileabilitiloca the ability to “open” a local repo clone or
78
+ switch branches in that clone. It only controls whether similar
79
+ operations over HTTP to a remote repo areto viewfor example,
80
+ since that basically amounts to opening a file in the remote repo.
81
+ also controls th
82
+ and [`/raw`][ru] URLs.file’s user category set is currently fixed. There is no way to define
83
+custom categories.
84
+
85
+These categories form a strict hierarchy. Mathematically speaking:
86
+all of/fossil-scm.org/home/fileabilitie?ci=8813ae91a699ac73&name=src%2Fm
87
+characters, one perations over
88
+`http[s]://` U
89
+ations over
90
+`http[s] dilocal fileadding a
91
+[**Se capability
92
+namenamenamenamenamenamenamenamenamenamecap].
93
+
94
+ The SSH Mnemonic: check
95
+ **i**nl fileadding a
96
+[**Se capability
97
+namenamenamenamenamenamenamenamenamenamecap].
98
+
99
+ The SSH client command defaults to “`ssh -e none -T`�*Se capability
100
+namenamenameMnemonic:
101
+ ileabilitie?ci=8813ae91a699ac73&name=src%2Fm
102
+characters, one perations over
103
+`http[s]://` U
104
+ations over
105
+`http[s] diffeCheck data out from Fossillocal fileadding a
106
+[**Se capability
107
+namenamenamenamenamenamenamenamenamenamecap].
108
+
109
+ l fileadding a
110
+[**Se capability
111
+namenamenamenamenamenamenamenamenamenamecap].
112
+
113
+ Thcapability
114
+namenamenamenamenamenamenamenamenamenamecap].
115
+
116
+ The SSH client command defaults to “`ssh -e none -T`” on most
117
+ platforms except Windows where it defaults to “`plink -ssh -T`”.
118
+ Yssh-command`
119
+ setticap]: https://fossil-scm.org/home/fileabilitie?ci=8813ae91a699ac73&name=src%2Fm
120
+characters, one perations over
121
+`http[s]://` U
122
+ations over
123
+`http[s] diffeCheck data out from Fossil/home/fileabilitiloca the ability to “open” a local repo clone or
124
+ switch branches in that clone. It only controls whether similar
125
+ operations over HTTP to a remote repo aret..Mnemonic: **w**rite
126
+ local fileadding a
127
+[**Se capability
128
+namenamenamenamenamenamenamenamenamenamecap].
129
+
130
+ The SSH client command defaults to “`ssh -e none -T`” on most
131
+ platforms except Windows where it defaults to “`plink ** — Same as [**3**
132
+
--- a/www/capabilities.md
+++ b/www/capabilities.md
@@ -0,0 +1,132 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
--- a/www/capabilities.md
+++ b/www/capabilities.md
@@ -0,0 +1,132 @@
1 local fileadding a
2 [**Se capability
3 namenamenamenamenamenamenamenamenamenamecap].
4
5 The SSH client command defaults to “`ssh -e none -T`” on most
6 platforms except Windows where it defaults to “`plink -ssh -T`”.
7 Yssh-command`
8 setticap]: https://fossil-scm.org/home/fileabilitie?ci=8813ae91a699ac73&name=src%2Fm
9 characters, one perations over
10 `http[s]://` U
11 ations over
12 `http[s] diffeCheck data out from Fossil/home/fileabilitiloca the ability to “open” a local repo clone or
13 switch branches in that clone. It only controls whether similar
14 operations over HTTP to a remote repo areto viewfor example,
15 since that basicallyamounts to opening a file in the remote repo.
16 also controls th
17 and [`/raw`][ru] URLs.file’s user category set is currently fixed. There is no way to define
18 custom categories.
19
20 These categories form a strict hierarchy. Mathematically speaking:
21 all of/fossil-scm.org/home/fileabilitie?ci=8813ae91a699ac73&name=src%2Fm
22 characters, one perations over
23 `http[s]://` U
24 ations over
25 `http[s] dilocal fileadding a
26 [**Se capability
27 namenamenamenamenamenamenamenamenamenamecap].
28
29 The SSH Mnemonic: check
30 **i**nl fileadding a
31 [**Se capability
32 namenamenamenamenamenamenamenamenamenamecap].
33
34 The SSH client command defaults to “`ssh -e none -T`�*Se capability
35 namenamenameMnemonic:
36 ileabilitie?ci=8813ae91a699ac73&name=src%2Fm
37 characters, one perations over
38 `http[s]://` U
39 ations over
40 `http[s] diffeCheck data out from Fossillocal fileadding a
41 [**Se capability
42 namenamenamenamenamenamenamenamenamenamecap].
43
44 l fileadding a
45 [**Se capability
46 namenamenamenamenamenamenamenamenamenamecap].
47
48 Thcapability
49 namenamenamenamenamenamenamenamenamenamecap].
50
51 The SSH client command defaults to “`ssh -e none -T`” on most
52 platforms except Windows where it defaults to “`plink -ssh -T`”.
53 Yssh-command`
54 setticap]: https://fossil-scm.org/home/fileabilitie?ci=8813ae91a699ac73&name=src%2Fm
55 characters, one perations over
56 `http[s]://` U
57 ations over
58 `http[s] diffeCheck data out from Fossil/home/fileabilitiloca the ability to “open” a local repo clone or
59 switch branches in that clone. It only controls whether similar
60 operations over HTTP to a remote repo aret..Mnemonic: **w**rite
61 local fileadding a
62 [**Se capability
63 namenamenamenamenamenamenamenamenamenamecap].
64
65 The SSH client command defaults to “`ssh -e none -T`” on most
66 platforms except Windows where it defaults to “`plink adding a
67 [**Se capability
68 namenamenamenamenamenamenamenamenamenamecap].
69
70 The SSH client command defaults to “`ssh -e none -T`” on most
71 platforms except Windows where it defaults to “`plink -ssh -T`”.
72 Yssh-command`
73 setticap]: https://fossil-scm.org/home/fileabilitie?ci=8813ae91a699ac73&name=src%2Fm
74 characters, one perations over
75 `http[s]://` U
76 ations over
77 `http[s] diffeCheck data out from Fossil/home/fileabilitiloca the ability to “open” a local repo clone or
78 switch branches in that clone. It only controls whether similar
79 operations over HTTP to a remote repo areto viewfor example,
80 since that basically amounts to opening a file in the remote repo.
81 also controls th
82 and [`/raw`][ru] URLs.file’s user category set is currently fixed. There is no way to define
83 custom categories.
84
85 These categories form a strict hierarchy. Mathematically speaking:
86 all of/fossil-scm.org/home/fileabilitie?ci=8813ae91a699ac73&name=src%2Fm
87 characters, one perations over
88 `http[s]://` U
89 ations over
90 `http[s] dilocal fileadding a
91 [**Se capability
92 namenamenamenamenamenamenamenamenamenamecap].
93
94 The SSH Mnemonic: check
95 **i**nl fileadding a
96 [**Se capability
97 namenamenamenamenamenamenamenamenamenamecap].
98
99 The SSH client command defaults to “`ssh -e none -T`�*Se capability
100 namenamenameMnemonic:
101 ileabilitie?ci=8813ae91a699ac73&name=src%2Fm
102 characters, one perations over
103 `http[s]://` U
104 ations over
105 `http[s] diffeCheck data out from Fossillocal fileadding a
106 [**Se capability
107 namenamenamenamenamenamenamenamenamenamecap].
108
109 l fileadding a
110 [**Se capability
111 namenamenamenamenamenamenamenamenamenamecap].
112
113 Thcapability
114 namenamenamenamenamenamenamenamenamenamecap].
115
116 The SSH client command defaults to “`ssh -e none -T`” on most
117 platforms except Windows where it defaults to “`plink -ssh -T`”.
118 Yssh-command`
119 setticap]: https://fossil-scm.org/home/fileabilitie?ci=8813ae91a699ac73&name=src%2Fm
120 characters, one perations over
121 `http[s]://` U
122 ations over
123 `http[s] diffeCheck data out from Fossil/home/fileabilitiloca the ability to “open” a local repo clone or
124 switch branches in that clone. It only controls whether similar
125 operations over HTTP to a remote repo aret..Mnemonic: **w**rite
126 local fileadding a
127 [**Se capability
128 namenamenamenamenamenamenamenamenamenamecap].
129
130 The SSH client command defaults to “`ssh -e none -T`” on most
131 platforms except Windows where it defaults to “`plink ** — Same as [**3**
132
M www/forum.wiki
+4 -28
--- www/forum.wiki
+++ www/forum.wiki
@@ -109,38 +109,14 @@
109109
110110
 <h2 id="setup">Setting up a Fossil Forum</h2>
111111
112112
 <h3 id="caps">Capabilities</h3>
113113
114
-Fossil forums use the same role-based access control mechanism as
115
-for normal Fossil repository logins.
116
-
117
-There are several dedicated forum-related capability bits you can grant
118
-a user:
119
-
120
- * <b>Read Forum</b> (<tt>2</tt>): The user may read forum posts.
121
-
122
- * <b>Write Forum</b> (<tt>3</tt>): The user may create new forum
123
- threads, reply to existing threads, and edit their own posts. New
124
- posts are held for moderation, and they are marked to prevent them
125
- from being included in clone and sync operations.
126
-
127
- * <b>WriteTrusted Forum</b> (<tt>4</tt>): Same as <b>Write Forum</b>
128
- except that forum updates bypass the [#moderation | moderation and
129
- private artifact restrictions].
130
-
131
- * <b>Moderate Forum</b> (<tt>5</tt>): User gets buttons on posts
132
- which allow them to either reject or approve posts held for
133
- moderation. User also gets access to a page (<tt>/modreq</tt>)
134
- showing the list of pending moderation tasks.
135
-
136
- * <b>Supervise Forum</b> (<tt>6</tt>): User can grant or revoke
137
- <b>WriteTrusted</b> capability for other users. (Currently
138
- unimplemented.)
139
-
140
- * <b>Email Alerts</b> (<tt>7</tt>): User can sign themselves up for
141
- email alerts, a.k.a. notifications.
114
+Fossil forums use the same [./capability.md | role-based access control
115
+mechanism] as for normal Fossil repository logins. There are
116
+[./capability.md#2 | several dedicated forum-related capabilities] you
117
+can grant to a user.
142118
143119
 By default, no Fossil user has permission to use the forums except for
144120
 users with Setup and Admin capabilities, which get these as part of the
145121
 large package of other capabilities they get.
146122
147123
--- www/forum.wiki
+++ www/forum.wiki
@@ -109,38 +109,14 @@
109
110 <h2 id="setup">Setting up a Fossil Forum</h2>
111
112 <h3 id="caps">Capabilities</h3>
113
114 Fossil forums use the same role-based access control mechanism as
115 for normal Fossil repository logins.
116
117 There are several dedicated forum-related capability bits you can grant
118 a user:
119
120 * <b>Read Forum</b> (<tt>2</tt>): The user may read forum posts.
121
122 * <b>Write Forum</b> (<tt>3</tt>): The user may create new forum
123 threads, reply to existing threads, and edit their own posts. New
124 posts are held for moderation, and they are marked to prevent them
125 from being included in clone and sync operations.
126
127 * <b>WriteTrusted Forum</b> (<tt>4</tt>): Same as <b>Write Forum</b>
128 except that forum updates bypass the [#moderation | moderation and
129 private artifact restrictions].
130
131 * <b>Moderate Forum</b> (<tt>5</tt>): User gets buttons on posts
132 which allow them to either reject or approve posts held for
133 moderation. User also gets access to a page (<tt>/modreq</tt>)
134 showing the list of pending moderation tasks.
135
136 * <b>Supervise Forum</b> (<tt>6</tt>): User can grant or revoke
137 <b>WriteTrusted</b> capability for other users. (Currently
138 unimplemented.)
139
140 * <b>Email Alerts</b> (<tt>7</tt>): User can sign themselves up for
141 email alerts, a.k.a. notifications.
142
143 By default, no Fossil user has permission to use the forums except for
144 users with Setup and Admin capabilities, which get these as part of the
145 large package of other capabilities they get.
146
147
--- www/forum.wiki
+++ www/forum.wiki
@@ -109,38 +109,14 @@
109
110 <h2 id="setup">Setting up a Fossil Forum</h2>
111
112 <h3 id="caps">Capabilities</h3>
113
114 Fossil forums use the same [./capability.md | role-based access control
115 mechanism] as for normal Fossil repository logins. There are
116 [./capability.md#2 | several dedicated forum-related capabilities] you
117 can grant to a user.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
118
119 By default, no Fossil user has permission to use the forums except for
120 users with Setup and Admin capabilities, which get these as part of the
121 large package of other capabilities they get.
122
123
M www/mkindex.tcl
+1
--- www/mkindex.tcl
+++ www/mkindex.tcl
@@ -18,10 +18,11 @@
1818
 blame.wiki {The Annotate/Blame Algorithm Of Fossil}
1919
 blockchain.md {Fossil As Blockchain}
2020
 branching.wiki {Branching, Forking, Merging, and Tagging}
2121
 bugtheory.wiki {Bug Tracking In Fossil}
2222
 build.wiki {Compiling and Installing Fossil}
23
+ capabilities.md {Administering User Capabilities}
2324
 cgi.wiki {CGI Script Configuration Options}
2425
 changes.wiki {Fossil Changelog}
2526
 checkin_names.wiki {Check-in And Version Names}
2627
 checkin.wiki {Check-in Checklist}
2728
 childprojects.wiki {Child Projects}
2829
--- www/mkindex.tcl
+++ www/mkindex.tcl
@@ -18,10 +18,11 @@
18 blame.wiki {The Annotate/Blame Algorithm Of Fossil}
19 blockchain.md {Fossil As Blockchain}
20 branching.wiki {Branching, Forking, Merging, and Tagging}
21 bugtheory.wiki {Bug Tracking In Fossil}
22 build.wiki {Compiling and Installing Fossil}
 
23 cgi.wiki {CGI Script Configuration Options}
24 changes.wiki {Fossil Changelog}
25 checkin_names.wiki {Check-in And Version Names}
26 checkin.wiki {Check-in Checklist}
27 childprojects.wiki {Child Projects}
28
--- www/mkindex.tcl
+++ www/mkindex.tcl
@@ -18,10 +18,11 @@
18 blame.wiki {The Annotate/Blame Algorithm Of Fossil}
19 blockchain.md {Fossil As Blockchain}
20 branching.wiki {Branching, Forking, Merging, and Tagging}
21 bugtheory.wiki {Bug Tracking In Fossil}
22 build.wiki {Compiling and Installing Fossil}
23 capabilities.md {Administering User Capabilities}
24 cgi.wiki {CGI Script Configuration Options}
25 changes.wiki {Fossil Changelog}
26 checkin_names.wiki {Check-in And Version Names}
27 checkin.wiki {Check-in Checklist}
28 childprojects.wiki {Child Projects}
29

Keyboard Shortcuts

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