Fossil SCM
Moved www/capabilities.md to www/caps/index.md and www/admin-v-setup.md to www/caps/admin-v-setup.md. Then broke three chunks of the old capabilities.md doc out into new www/caps/* docs: login groups, implementation details of user capabilities, and the user capability reference material. The latter switched from Markdown to HTML format so we could make it a clearer-looking table, rather than its prior hard-to-read bullet list form.
Commit
c6cdf9ce8e95df14ab30255f3d98a91f070de2cc1ae009aade5642a0fb29dc7f
Parent
ee901c7be39e4b9…
9 files changed
-9
-219
+5
-5
+1
+47
-163
+6
+90
+4
-2
+16
-7
D
www/admin-v-setup.md
-9
| --- a/www/admin-v-setup.md | ||
| +++ b/www/admin-v-setup.md | ||
| @@ -1,9 +0,0 @@ | ||
| 1 | -# Differences B Capabilitiestween Sthe power hierarcKeep in mind that | |
| 2 | -which means that a usuknown tomight haveevauThe exception to this is when the clone is done as a Setup capabilities.md. In this way, /antibot.wiki) | |
| 3 | - | |
| 4 | -[au]: geable clones. This is useful not o, it is a useful element of a load balancing and | |
| 5 | -failover system# Differenccapabilitiefferences Between Sthe power hierarchy laid out at tblock | |
| 6 | -chain][bc], blockchainblockchainblockchainTH [`fossil | |
| 7 | - (“y”) | |
| 8 | - ’s discretion“y” capthis powerful capability(./shunning.wiki)(./blockchain.md)./alerts.md**WrUnver**](./ref.html#y). (That lone hold-out is [by design][snoy].)capabilitiescapabilities.md#grouph1]:th1.mdfferences Btween Sthe power hiera power hierarcKeep in mind that | |
| 9 | -wh |
| --- a/www/admin-v-setup.md | |
| +++ b/www/admin-v-setup.md | |
| @@ -1,9 +0,0 @@ | |
| 1 | # Differences B Capabilitiestween Sthe power hierarcKeep in mind that |
| 2 | which means that a usuknown tomight haveevauThe exception to this is when the clone is done as a Setup capabilities.md. In this way, /antibot.wiki) |
| 3 | |
| 4 | [au]: geable clones. This is useful not o, it is a useful element of a load balancing and |
| 5 | failover system# Differenccapabilitiefferences Between Sthe power hierarchy laid out at tblock |
| 6 | chain][bc], blockchainblockchainblockchainTH [`fossil |
| 7 | (“y”) |
| 8 | ’s discretion“y” capthis powerful capability(./shunning.wiki)(./blockchain.md)./alerts.md**WrUnver**](./ref.html#y). (That lone hold-out is [by design][snoy].)capabilitiescapabilities.md#grouph1]:th1.mdfferences Btween Sthe power hiera power hierarcKeep in mind that |
| 9 | wh |
| --- a/www/admin-v-setup.md | |
| +++ b/www/admin-v-setup.md | |
| @@ -1,9 +0,0 @@ | |
D
www/capabilities.md
-219
| --- a/www/capabilities.md | ||
| +++ b/www/capabilities.md | ||
| @@ -1,219 +0,0 @@ | ||
| 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] different capabilities. We | |
| 13 | -explain how we came to assign each character [below](#impl).when working on a clone done over such a path, | |
| 14 | -except thAsat there are | |
| 15 | - | |
| 16 | -[sync][sy[sync]: /help?cmd=synchen | |
| 17 | - | |
| 18 | -local clone, | |
| 19 | - | |
| 20 | -is on the local file system. If you can log into the remote system over | |
| 21 | - on that | |
| 22 | -, it isfor `file://` URLs. | |
| 23 | - | |
| 24 | -All��. | |
| 25 | - Yssh-command` | |
| 26 | - selocal fileadd | |
| 27 | -ie without cap checks. The SSH client defaults to “`ssh | |
| 28 | - -e none -T`” on most platforms, except on Windows where it defaults | |
| 29 | - ,n’t do this | |
| 30 | - withBecause both mechanisms work on local repos, the checks for capabilities | |
| 31 | -for | |
| 32 | -such URLs can never return “false,” because you are the [**S(#group)ecause you are the [**Setup**][s] | |
| 33 | -user on both sides of the conversation. Such check | |
| 34 | -effect ddd][d][e][e][i][i]**: delete,cmdcmdcmdcmdcmdcmdyour user is effectivelyuser][apsu] on both sides of the SSH connection. | |
| 35 | - | |
| 36 | -Fossil reuses the HTTP-based [sync protocol][sp] in both cases above, | |
| 37 | -tunnelling HTTP through an OS pipe or through SSH (FIXME?), but because | |
| 38 | - are | |
| 39 | -done against your effective Setup user on the other repo, the check only | |
| 40 | -has an cmd(../embeddeddoc.wiki) | |
| 41 | - Yssh-command` | |
| 42 | - setticap]: https://f repo | |
| 43 | -that’s mais://fossil-scm.org/home/file?ci=8813ae91a699ac73&name=src%2Fmain.c&ln=2632-2637User caps only affect Fossil’s [UI pages][wp], remote operations over | |
| 44 | -`http[s]://` URLs, and [the JSON API][japi]. | |
| 45 | - | |
| 46 | -User caps *do not* affect operations done on a local repo opened via a | |
| 47 | -`file://` URL or a file system path. as sensible: | |
| 48 | -only localmatter when operating on a local SQLite DB | |
| 49 | -file. The same is tr(#u)e over such a path, | |
| 50 | -except th(#v)local fileadding a | |
| 51 | -[**Se capability | |
| 52 | -namenamenamenamenamenamenamenamenamenamecap]. | |
| 53 | - | |
| 54 | - The SSH client command defaults to “`ssh -e none -T`” on most | |
| 55 | - platforms except Windows where it defaults to “`plink -ssh -T`”. | |
| 56 | - Yssh-command` | |
| 57 | - setticap]: https://fossil-scm.org/home/file?ci=8813ae91a699ac73&name=src%2Fmain.c&ln=2632-263eadding a | |
| 58 | -[**Se capability | |
| 59 | -namenamenamenamenamenamenamenamenamenamecap]. | |
| 60 | - | |
| 61 | - The SSH client command defaults to “`ssh -e none -T`” on most | |
| 62 | - platforms except Windows where it defaults to “`plink -ssh -T`”. | |
| 63 | - Yssh-command` | |
| 64 | - setticap]: https://fossil-scm.org/home/file?ci=8813ae91a699ac73&name=src%2Fmain.c&ln=2632-2637User caps only affect Fossil’s [UI pages][wp], remote operations over | |
| 65 | -`http[s]://` URLs, and [the JSON API][japi]. | |
| 66 | - | |
| 67 | -User caps *do not* affect operations done on a local repo opened via a | |
| 68 | -`file://` URL or a file system path. as sensible: | |
| 69 | -only localmatter when operating on a local SQLite DB | |
| 70 | -file. The same is true when working on a clone done over such a path, | |
| 71 | -except thAsat there are | |
| 72 | - | |
| 73 | -[sync][sync] with | |
| 74 | -effectively | |
| 75 | -both sides of the sync. | |
| 76 | - | |
| 77 | -What may surprise you is that user caps *also do not affect SSH!* When | |
| 78 | - | |
| 79 | -local clone, | |
| 80 | - | |
| 81 | -is on the local file system. If you can log into the remote system over | |
| 82 | - on that | |
| 83 | -, it isfor `file://` URLs. | |
| 84 | - | |
| 85 | -Ad [the JSON API][japi]. | |
| 86 | - | |
| 87 | -User caps *do not* affect operations done on a local repo opened via a | |
| 88 | -`file://` URL or a file system path. as sensible: | |
| 89 | -only localmatter when operating on a local SQLite DB | |
| 90 | -file.For | |
| 91 | -the most part, you want to simply read the [reference material | |
| 92 | -below](#ref)r such a path, | |
| 93 | -except thAsat there are | |
| 94 | - | |
| 95 | -[sync][sync] with | |
| 96 | -effectively | |
| 97 | -both sides of the sync. | |
| 98 | - | |
| 99 | -What may surprise you is that user caps *also do not affect SSH!* When | |
| 100 | - | |
| 101 | -local clone, | |
| 102 | - | |
| 103 | -is on the local file system. If you can log into the remote system over | |
| 104 | - on that | |
| 105 | -, it isfor `file://` URLs. | |
| 106 | - | |
| 107 | -All��. | |
| 108 | - local fileadding a | |
| 109 | -[**Se capability | |
| 110 | -namenamenamenamenamenamenamenamenamenamecap]. | |
| 111 | - | |
| 112 | - The SSH client command defaults to “`ssh -e none -T`” on most | |
| 113 | -This is unavoidable because those check-ins are already written durably | |
| 114 | -t user(s)](#a). Both are | |
| 115 | -(#l), [ticket](#q), and [forum](#5)(#7)(#g)[j](#j)[o](#o)[r](#r)[z](#z)(#h)[m](#m)[n](#n)[c](#c)(#k)[p](#p)[t](#t)[w](#w)(#d)[e](#e)[i](#i)group"></a>Login Groups | |
| 116 | - | |
| 117 | -The Admin → Login-Groups UI feature and its corresponding [`login-group` | |
| 118 | -command][lg] solve a common problem with Fossil: you’ve created multiple | |
| 119 | -repositories that some set of users all need access to, those users all | |
| 120 | -have the same access level on all of these shared repositories, and you | |
| 121 | -don’t want to redundantly configure the user set for each repository. | |
| 122 | - | |
| 123 | -This feature ties changes to the “`user`” table in one repo to that in | |
| 124 | -one or more other repos. With this configured, you get a new choice on | |
| 125 | -the user edit screen, offering to make changes specific to the one | |
| 126 | -repository only or to apply it to all others in the login group as well. | |
| 127 | - | |
| 128 | -A user can log into one repo in a login group only if that user has an | |
| 129 | -entry in that repo’s user table. That is, setting up a login group | |
| 130 | -doesn’t automatically transfer all user accounts from the joined repo to | |
| 131 | -the joining repo. Only when a user exists by name in both repos will | |
| 132 | -that user be able to share credentials across the repos. | |
| 133 | - | |
| 134 | -Login groups can have names, allowing one “master” repo to host multiple | |
| 135 | -subsets of its users to other repos. | |
| 136 | - | |
| 137 | -Trust in login groups is transitive within a single server. If repo C | |
| 138 | -joined repo B and repo B joined A, changes in C’s user table affect both | |
| 139 | -A and B, if you tell Fossil that the change applies to all repos in the | |
| 140 | -login group. | |
| 141 | - | |
| 142 | -[](#defuser) (#group)all of | |
| 143 | -the user cap checks in Fossil are on its web interfaces only. | |
| 144 | - | |
| 145 | -TODO: Why then can I not `/xfer` my local repo contents to a remote repo | |
| 146 | -without logging in?/sync.wiki | |
| 147 | - | |
| 148 | -## <a name="ref"></a>Capability Reference | |
| 149 | - | |
| 150 | -This section documents each currently-defined usery character | |
| 151 | -in more detail than the brief summary on the [user capability “key” | |
| 152 | -page](/setup_ucap_list). Each entry begins with the capability letter | |
| 153 | -used in the Fossil user editor followed by the C code’s name for that | |
| 154 | -cap within the `FossilUserPerms` object. | |
| 155 | - | |
| 156 | -The [mnemonics][mn] given here vary from obviously-correct to *post | |
| 157 | -facto* rationalizations to the outright fanciful. To [some | |
| 158 | -extent](#choices), this is unavoidable. | |
| 159 | - | |
| 160 | -* <a name="a"></a>**a (Admin)** — Admin users have *all* of the capabilities | |
| 161 | - below except for [setup](#s). See [Admin vs. Setup][avs] for a more | |
| 162 | - nuanced discussion. Mnemonic: **a**dministrate. | |
| 163 | - | |
| 164 | -* b"></a>**b (Attach)** — Add attachments to wiki articles or tickets. | |
| 165 | - Mnemonics: **b**ind, **b**utton, **b**ond, or **b**olt. | |
| 166 | - | |
| 167 | -* <a name="c"></a>**c (ApndTkt)** — Append comments to existing tickets. | |
| 168 | - Mnemonic: **c**omment. | |
| 169 | - | |
| 170 | -* <a name="d"></a>**d (Delete)** — Delete wiki articles or tickets. Mnemonic: | |
| 171 | - **d**elete. | |
| 172 | - | |
| 173 | -* <a name="e"></a>**e (RdAddr)** — View [personal identifying information][pii] | |
| 174 | - (PII) about other users such as email addresses. Mnemonics: show | |
| 175 | - **e**mail addresses; or **E**urope, home of [GDPR][gdpr]. | |
| 176 | - | |
| 177 | -* <a name="f"></a>**f (NewWiki)** — Create new wiki articles. Mnemonic: | |
| 178 | - **f**ast, English translation of the Hawaiian word [*wiki*][wnh]. | |
| 179 | - | |
| 180 | -* <a name="g"></a>**g (Clone)** — Clone the repository. Note that this is | |
| 181 | - distinct from [check-out capability, **o**](#o). Mnemonic: **g**et. | |
| 182 | - | |
| 183 | -* <a name="h"></a>**h (Hyperlink)** — Get hyperlinks in generated HTML which link | |
| 184 | - you to other parts of the repository. This capability exists and is | |
| 185 | - disabled by default for/` URLs, and [the JSON API to [prevent bots from | |
| 186 | - wandering around aimlessly][bot] in the site’s hyperlink web, | |
| 187 | - chewing up server resources to little good purpose. Mnemonic: | |
| 188 | - **h**yperlink. | |
| 189 | - | |
| 190 | -* <a name="i"></a>**i (Write)** — Check changes into the repository. Note that | |
| 191 | - a lack of this capability does not prevent you from checking changes | |
| 192 | - into your local clone, only from syncing those changes up to the | |
| 193 | - parent repo, and then [only over HTTP](#webonly). Granting this | |
| 194 | - capability also grants **o (Read)**. Mnemonic: check **i**n | |
| 195 | - changes. | |
| 196 | - | |
| 197 | -* <a name="j"></a>**j (RdWiki)** — View wiki articles. Mnemonic: in**j**est | |
| 198 | - page content. (All right, you critics, you do better, then.) | |
| 199 | - | |
| 200 | -* <a name="k"></a>**k (WrWiki)** — Edit wiki articles. Granting this | |
| 201 | - capability also grants **j (RdWiki)** and **m (ApndWiki)**, but it | |
| 202 | - does *not* grant **f (NewWiki)**! Mnemonic: **k**ontribute. | |
| 203 | - | |
| 204 | -* <a name="l"></a>**l (ModWiki)** — Moderate [wiki article appends](#m). Appends | |
| 205 | - do not get saved permamently to the receiving repo’s block chain | |
| 206 | - until some user (one with this cap or [Setup cap](#s)) approves it. | |
| 207 | - Mnemonic: a**l**low. | |
| 208 | - | |
| 209 | -* <a name="m"></a>**m (ApndWiki)** — Append content to existing wiki articles. | |
| 210 | - Mmnemonics: a**m**end or **m**odify. | |
| 211 | - | |
| 212 | -* <a name="n"></a>**n (NewTkt)** — File new tickets. Mnemonic: **n**ew ticket. | |
| 213 | - | |
| 214 | -* <a name="o"></a>**o (Read)** — Read repository content from a remote | |
| 215 | - Fossil instance over HTTP. This | |
| 216 | - reading data from a local | |
| 217 | - web interfaces | |
| 218 | - | |
| 219 | - of whether your user |
| --- a/www/capabilities.md | |
| +++ b/www/capabilities.md | |
| @@ -1,219 +0,0 @@ | |
| 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] different capabilities. We |
| 13 | explain how we came to assign each character [below](#impl).when working on a clone done over such a path, |
| 14 | except thAsat there are |
| 15 | |
| 16 | [sync][sy[sync]: /help?cmd=synchen |
| 17 | |
| 18 | local clone, |
| 19 | |
| 20 | is on the local file system. If you can log into the remote system over |
| 21 | on that |
| 22 | , it isfor `file://` URLs. |
| 23 | |
| 24 | All��. |
| 25 | Yssh-command` |
| 26 | selocal fileadd |
| 27 | ie without cap checks. The SSH client defaults to “`ssh |
| 28 | -e none -T`” on most platforms, except on Windows where it defaults |
| 29 | ,n’t do this |
| 30 | withBecause both mechanisms work on local repos, the checks for capabilities |
| 31 | for |
| 32 | such URLs can never return “false,” because you are the [**S(#group)ecause you are the [**Setup**][s] |
| 33 | user on both sides of the conversation. Such check |
| 34 | effect ddd][d][e][e][i][i]**: delete,cmdcmdcmdcmdcmdcmdyour user is effectivelyuser][apsu] on both sides of the SSH connection. |
| 35 | |
| 36 | Fossil reuses the HTTP-based [sync protocol][sp] in both cases above, |
| 37 | tunnelling HTTP through an OS pipe or through SSH (FIXME?), but because |
| 38 | are |
| 39 | done against your effective Setup user on the other repo, the check only |
| 40 | has an cmd(../embeddeddoc.wiki) |
| 41 | Yssh-command` |
| 42 | setticap]: https://f repo |
| 43 | that’s mais://fossil-scm.org/home/file?ci=8813ae91a699ac73&name=src%2Fmain.c&ln=2632-2637User caps only affect Fossil’s [UI pages][wp], remote operations over |
| 44 | `http[s]://` URLs, and [the JSON API][japi]. |
| 45 | |
| 46 | User caps *do not* affect operations done on a local repo opened via a |
| 47 | `file://` URL or a file system path. as sensible: |
| 48 | only localmatter when operating on a local SQLite DB |
| 49 | file. The same is tr(#u)e over such a path, |
| 50 | except th(#v)local fileadding a |
| 51 | [**Se capability |
| 52 | namenamenamenamenamenamenamenamenamenamecap]. |
| 53 | |
| 54 | The SSH client command defaults to “`ssh -e none -T`” on most |
| 55 | platforms except Windows where it defaults to “`plink -ssh -T`”. |
| 56 | Yssh-command` |
| 57 | setticap]: https://fossil-scm.org/home/file?ci=8813ae91a699ac73&name=src%2Fmain.c&ln=2632-263eadding a |
| 58 | [**Se capability |
| 59 | namenamenamenamenamenamenamenamenamenamecap]. |
| 60 | |
| 61 | The SSH client command defaults to “`ssh -e none -T`” on most |
| 62 | platforms except Windows where it defaults to “`plink -ssh -T`”. |
| 63 | Yssh-command` |
| 64 | setticap]: https://fossil-scm.org/home/file?ci=8813ae91a699ac73&name=src%2Fmain.c&ln=2632-2637User caps only affect Fossil’s [UI pages][wp], remote operations over |
| 65 | `http[s]://` URLs, and [the JSON API][japi]. |
| 66 | |
| 67 | User caps *do not* affect operations done on a local repo opened via a |
| 68 | `file://` URL or a file system path. as sensible: |
| 69 | only localmatter when operating on a local SQLite DB |
| 70 | file. The same is true when working on a clone done over such a path, |
| 71 | except thAsat there are |
| 72 | |
| 73 | [sync][sync] with |
| 74 | effectively |
| 75 | both sides of the sync. |
| 76 | |
| 77 | What may surprise you is that user caps *also do not affect SSH!* When |
| 78 | |
| 79 | local clone, |
| 80 | |
| 81 | is on the local file system. If you can log into the remote system over |
| 82 | on that |
| 83 | , it isfor `file://` URLs. |
| 84 | |
| 85 | Ad [the JSON API][japi]. |
| 86 | |
| 87 | User caps *do not* affect operations done on a local repo opened via a |
| 88 | `file://` URL or a file system path. as sensible: |
| 89 | only localmatter when operating on a local SQLite DB |
| 90 | file.For |
| 91 | the most part, you want to simply read the [reference material |
| 92 | below](#ref)r such a path, |
| 93 | except thAsat there are |
| 94 | |
| 95 | [sync][sync] with |
| 96 | effectively |
| 97 | both sides of the sync. |
| 98 | |
| 99 | What may surprise you is that user caps *also do not affect SSH!* When |
| 100 | |
| 101 | local clone, |
| 102 | |
| 103 | is on the local file system. If you can log into the remote system over |
| 104 | on that |
| 105 | , it isfor `file://` URLs. |
| 106 | |
| 107 | All��. |
| 108 | local fileadding a |
| 109 | [**Se capability |
| 110 | namenamenamenamenamenamenamenamenamenamecap]. |
| 111 | |
| 112 | The SSH client command defaults to “`ssh -e none -T`” on most |
| 113 | This is unavoidable because those check-ins are already written durably |
| 114 | t user(s)](#a). Both are |
| 115 | (#l), [ticket](#q), and [forum](#5)(#7)(#g)[j](#j)[o](#o)[r](#r)[z](#z)(#h)[m](#m)[n](#n)[c](#c)(#k)[p](#p)[t](#t)[w](#w)(#d)[e](#e)[i](#i)group"></a>Login Groups |
| 116 | |
| 117 | The Admin → Login-Groups UI feature and its corresponding [`login-group` |
| 118 | command][lg] solve a common problem with Fossil: you’ve created multiple |
| 119 | repositories that some set of users all need access to, those users all |
| 120 | have the same access level on all of these shared repositories, and you |
| 121 | don’t want to redundantly configure the user set for each repository. |
| 122 | |
| 123 | This feature ties changes to the “`user`” table in one repo to that in |
| 124 | one or more other repos. With this configured, you get a new choice on |
| 125 | the user edit screen, offering to make changes specific to the one |
| 126 | repository only or to apply it to all others in the login group as well. |
| 127 | |
| 128 | A user can log into one repo in a login group only if that user has an |
| 129 | entry in that repo’s user table. That is, setting up a login group |
| 130 | doesn’t automatically transfer all user accounts from the joined repo to |
| 131 | the joining repo. Only when a user exists by name in both repos will |
| 132 | that user be able to share credentials across the repos. |
| 133 | |
| 134 | Login groups can have names, allowing one “master” repo to host multiple |
| 135 | subsets of its users to other repos. |
| 136 | |
| 137 | Trust in login groups is transitive within a single server. If repo C |
| 138 | joined repo B and repo B joined A, changes in C’s user table affect both |
| 139 | A and B, if you tell Fossil that the change applies to all repos in the |
| 140 | login group. |
| 141 | |
| 142 | [](#defuser) (#group)all of |
| 143 | the user cap checks in Fossil are on its web interfaces only. |
| 144 | |
| 145 | TODO: Why then can I not `/xfer` my local repo contents to a remote repo |
| 146 | without logging in?/sync.wiki |
| 147 | |
| 148 | ## <a name="ref"></a>Capability Reference |
| 149 | |
| 150 | This section documents each currently-defined usery character |
| 151 | in more detail than the brief summary on the [user capability “key” |
| 152 | page](/setup_ucap_list). Each entry begins with the capability letter |
| 153 | used in the Fossil user editor followed by the C code’s name for that |
| 154 | cap within the `FossilUserPerms` object. |
| 155 | |
| 156 | The [mnemonics][mn] given here vary from obviously-correct to *post |
| 157 | facto* rationalizations to the outright fanciful. To [some |
| 158 | extent](#choices), this is unavoidable. |
| 159 | |
| 160 | * <a name="a"></a>**a (Admin)** — Admin users have *all* of the capabilities |
| 161 | below except for [setup](#s). See [Admin vs. Setup][avs] for a more |
| 162 | nuanced discussion. Mnemonic: **a**dministrate. |
| 163 | |
| 164 | * b"></a>**b (Attach)** — Add attachments to wiki articles or tickets. |
| 165 | Mnemonics: **b**ind, **b**utton, **b**ond, or **b**olt. |
| 166 | |
| 167 | * <a name="c"></a>**c (ApndTkt)** — Append comments to existing tickets. |
| 168 | Mnemonic: **c**omment. |
| 169 | |
| 170 | * <a name="d"></a>**d (Delete)** — Delete wiki articles or tickets. Mnemonic: |
| 171 | **d**elete. |
| 172 | |
| 173 | * <a name="e"></a>**e (RdAddr)** — View [personal identifying information][pii] |
| 174 | (PII) about other users such as email addresses. Mnemonics: show |
| 175 | **e**mail addresses; or **E**urope, home of [GDPR][gdpr]. |
| 176 | |
| 177 | * <a name="f"></a>**f (NewWiki)** — Create new wiki articles. Mnemonic: |
| 178 | **f**ast, English translation of the Hawaiian word [*wiki*][wnh]. |
| 179 | |
| 180 | * <a name="g"></a>**g (Clone)** — Clone the repository. Note that this is |
| 181 | distinct from [check-out capability, **o**](#o). Mnemonic: **g**et. |
| 182 | |
| 183 | * <a name="h"></a>**h (Hyperlink)** — Get hyperlinks in generated HTML which link |
| 184 | you to other parts of the repository. This capability exists and is |
| 185 | disabled by default for/` URLs, and [the JSON API to [prevent bots from |
| 186 | wandering around aimlessly][bot] in the site’s hyperlink web, |
| 187 | chewing up server resources to little good purpose. Mnemonic: |
| 188 | **h**yperlink. |
| 189 | |
| 190 | * <a name="i"></a>**i (Write)** — Check changes into the repository. Note that |
| 191 | a lack of this capability does not prevent you from checking changes |
| 192 | into your local clone, only from syncing those changes up to the |
| 193 | parent repo, and then [only over HTTP](#webonly). Granting this |
| 194 | capability also grants **o (Read)**. Mnemonic: check **i**n |
| 195 | changes. |
| 196 | |
| 197 | * <a name="j"></a>**j (RdWiki)** — View wiki articles. Mnemonic: in**j**est |
| 198 | page content. (All right, you critics, you do better, then.) |
| 199 | |
| 200 | * <a name="k"></a>**k (WrWiki)** — Edit wiki articles. Granting this |
| 201 | capability also grants **j (RdWiki)** and **m (ApndWiki)**, but it |
| 202 | does *not* grant **f (NewWiki)**! Mnemonic: **k**ontribute. |
| 203 | |
| 204 | * <a name="l"></a>**l (ModWiki)** — Moderate [wiki article appends](#m). Appends |
| 205 | do not get saved permamently to the receiving repo’s block chain |
| 206 | until some user (one with this cap or [Setup cap](#s)) approves it. |
| 207 | Mnemonic: a**l**low. |
| 208 | |
| 209 | * <a name="m"></a>**m (ApndWiki)** — Append content to existing wiki articles. |
| 210 | Mmnemonics: a**m**end or **m**odify. |
| 211 | |
| 212 | * <a name="n"></a>**n (NewTkt)** — File new tickets. Mnemonic: **n**ew ticket. |
| 213 | |
| 214 | * <a name="o"></a>**o (Read)** — Read repository content from a remote |
| 215 | Fossil instance over HTTP. This |
| 216 | reading data from a local |
| 217 | web interfaces |
| 218 | |
| 219 | of whether your user |
| --- a/www/capabilities.md | |
| +++ b/www/capabilities.md | |
| @@ -1,219 +0,0 @@ | |
+5
-5
| --- a/www/caps/admin-v-setup.md | ||
| +++ b/www/caps/admin-v-setup.md | ||
| @@ -1,9 +1,9 @@ | ||
| 1 | -# Differences B Capabilitiestween Sthe power hierarcKeep in mind that | |
| 2 | -which means that a usuknown tomight haveevauThe exception to this is when the clone is done as a Setup capabilities.md. In this way, /antibot.wiki) | |
| 1 | +# Differences Btween Sthe power hierarcKeep in mind that | |
| 2 | +which means that a usuknown tomight haveevauThe exception to this is when the clone is done as a Setup user, since | |
| 3 | +this also copiesthe `user` table on theies. In this way, /antibot.wiki) | |
| 3 | 4 | |
| 4 | 5 | [au]: geable clones. This is useful not o, it is a useful element of a load balancing and |
| 5 | -failover system# Differenccapabilitiefferences Between Sthe power hierarchy laid out at tblock | |
| 6 | +failover system# Differences Between Sthe power hierarchy laid out at tblock | |
| 6 | 7 | chain][bc], blockchainblockchainblockchainTH [`fossil |
| 7 | 8 | (“y”) |
| 8 | - ’s discretion“y” capthis powerful capability(./shunning.wiki)(./blockchain.md)./alerts.md**WrUnver**](./ref.html#y). (That lone hold-out is [by design][snoy].)capabilitiescapabilities.md#grouph1]:th1.mdfferences Btween Sthe power hiera power hierarcKeep in mind that | |
| 9 | -wh | |
| 9 | + ’s discretion“y” capthis powerful capability(./shunning.wiki)(./blockchain.md)./alerts.md**WrUnver**](./ref.html#y). (That lone hold-out is [by design][snoy].) |
| --- a/www/caps/admin-v-setup.md | |
| +++ b/www/caps/admin-v-setup.md | |
| @@ -1,9 +1,9 @@ | |
| 1 | # Differences B Capabilitiestween Sthe power hierarcKeep in mind that |
| 2 | which means that a usuknown tomight haveevauThe exception to this is when the clone is done as a Setup capabilities.md. In this way, /antibot.wiki) |
| 3 | |
| 4 | [au]: geable clones. This is useful not o, it is a useful element of a load balancing and |
| 5 | failover system# Differenccapabilitiefferences Between Sthe power hierarchy laid out at tblock |
| 6 | chain][bc], blockchainblockchainblockchainTH [`fossil |
| 7 | (“y”) |
| 8 | ’s discretion“y” capthis powerful capability(./shunning.wiki)(./blockchain.md)./alerts.md**WrUnver**](./ref.html#y). (That lone hold-out is [by design][snoy].)capabilitiescapabilities.md#grouph1]:th1.mdfferences Btween Sthe power hiera power hierarcKeep in mind that |
| 9 | wh |
| --- a/www/caps/admin-v-setup.md | |
| +++ b/www/caps/admin-v-setup.md | |
| @@ -1,9 +1,9 @@ | |
| 1 | # Differences Btween Sthe power hierarcKeep in mind that |
| 2 | which means that a usuknown tomight haveevauThe exception to this is when the clone is done as a Setup user, since |
| 3 | this also copiesthe `user` table on theies. In this way, /antibot.wiki) |
| 4 | |
| 5 | [au]: geable clones. This is useful not o, it is a useful element of a load balancing and |
| 6 | failover system# Differences Between Sthe power hierarchy laid out at tblock |
| 7 | chain][bc], blockchainblockchainblockchainTH [`fossil |
| 8 | (“y”) |
| 9 | ’s discretion“y” capthis powerful capability(./shunning.wiki)(./blockchain.md)./alerts.md**WrUnver**](./ref.html#y). (That lone hold-out is [by design][snoy].) |
+1
| --- a/www/caps/impl.md | ||
| +++ b/www/caps/impl.md | ||
| @@ -0,0 +1 @@ | ||
| 1 | +# Implementation Details on |
| --- a/www/caps/impl.md | |
| +++ b/www/caps/impl.md | |
| @@ -0,0 +1 @@ | |
| --- a/www/caps/impl.md | |
| +++ b/www/caps/impl.md | |
| @@ -0,0 +1 @@ | |
| 1 | # Implementation Details on |
+47
-163
| --- a/www/caps/index.md | ||
| +++ b/www/caps/index.md | ||
| @@ -1,60 +1,4 @@ | ||
| 1 | 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] different capabilities. We | |
| 13 | -explain how we came to assign each character [below](#impl).when working on a clone done over such a path, | |
| 14 | -except thAsat there are | |
| 15 | - | |
| 16 | -[sync][sy[sync]: /help?cmd=synchen | |
| 17 | - | |
| 18 | -local clone, | |
| 19 | - | |
| 20 | -is on the local file system. If you can log into the remote system over | |
| 21 | - on that | |
| 22 | -, it isfor `file://` URLs. | |
| 23 | - | |
| 24 | -All��. | |
| 25 | - Yssh-command` | |
| 26 | - selocal fileadd | |
| 27 | -ie without cap checks. The SSH client defaults to “`ssh | |
| 28 | - -e none -T`” on most platforms, except on Windows where it defaults | |
| 29 | - ,n’t do this | |
| 30 | - withBecause both mechanisms work on local repos, the checks for capabilities | |
| 31 | -for | |
| 32 | -such URLs can never return “false,” because you are the [**S(#group)ecause you are the [**Setup**][s] | |
| 33 | -user on both sides of the conversation. Such check | |
| 34 | -effect ddd][d][e][e][i][i]**: delete,cmdcmdcmdcmdcmdcmdyour user is effectivelyuser][apsu] on both sides of the SSH connection. | |
| 35 | - | |
| 36 | -Fossil reuses the HTTP-based [sync protocol][sp] in both cases above, | |
| 37 | -tunnelling HTTP through an OS pipe or through SSH (FIXME?), but because | |
| 38 | - are | |
| 39 | -done against your effective Setup user on the other repo, the check only | |
| 40 | -has an cmd(../embeddeddoc.wiki) | |
| 41 | - Yssh-command` | |
| 42 | - setticap]: https://f repo | |
| 43 | -that’s mais://fossil-scm.org/home/file?ci=8813ae91a699ac73&name=src%2Fmain.c&ln=2632-2637User caps only affect Fossil’s [UI pages][wp], remote operations over | |
| 44 | -`http[s]://` URLs, and [the JSON API][japi]. | |
| 45 | - | |
| 46 | -User caps *do not* affect operations done on a local repo opened via a | |
| 47 | -`file://` URL or a file system path. as sensible: | |
| 48 | -only localmatter when operating on a local SQLite DB | |
| 49 | -file. The same is tr(#u)e over such a path, | |
| 50 | -except th(#v)local fileadding a | |
| 51 | -[**Se capability | |
| 52 | -namenamenamenamenamenamenamenamenamenamecap]. | |
| 53 | - | |
| 54 | - The SSH client command defaults to “`ssh -e none -T`” on most | |
| 55 | - platforms except Windows where it defaults to “`plink -ssh -T`”. | |
| 56 | - Yssh-command` | |
| 57 | - setticap]: https://fossil-scm.org/home/file?ci=8813ae91a699ac73&name=src%2Fmain.c&ln=2632-263eadding a | |
| 58 | 2 | [**Se capability |
| 59 | 3 | namenamenamenamenamenamenamenamenamenamecap]. |
| 60 | 4 | |
| @@ -82,14 +26,32 @@ | ||
| 82 | 26 | on that |
| 83 | 27 | , it isfor `file://` URLs. |
| 84 | 28 | |
| 85 | -Ad [the JSON API][japi]. | |
| 29 | +All��. | |
| 30 | + Yssh-command` | |
| 31 | + selocal fileadd | |
| 32 | +ie without cap checks. The SSH client defaults to “`ssh | |
| 33 | + -e none -T`” on most platforms, except on Windows where it defaults | |
| 34 | + ,n’t do this | |
| 35 | + withBecause both mechanisms work on local repos, the checks for capabilities | |
| 36 | +for | |
| 37 | +such URLs can never return “false,” because you are the [**Setup**][s] | |
| 38 | +user on both sides of the conversation. Such check | |
| 39 | +effect ddd][d][e][e][i][i]**: delete,cmdcmdcmdcmdcmdcmdyour user is effectivelyuser][apsu] on both sides of the SSH connection. | |
| 40 | + | |
| 41 | +Fossil reuses the HTTP-based [sync protocol][sp] in both cases above, | |
| 42 | +tunnelling HTTP through an OS pipe or through SSH (FIXME?), but because | |
| 43 | + are | |
| 44 | +done against your effective Setup user on the other repo, the check only | |
| 45 | +has an cmd(../embeddeddoc.wiki) | |
| 46 | + Yssh-command` | |
| 47 | + setticap]: https://f repo | |
| 48 | +that’s mais://fossil-scm.org/home/file?ci=8813ae91a699ac73&name=src%2Fmain.c&ln=2632-2637User caps only affect Fossil’s [UI pages][wp], remote operations over | |
| 49 | +`http[s]://` URLs, and [the JSON API][japi]. | |
| 86 | 50 | |
| 87 | 51 | User caps *do not* affect operations done on a local repo opened via a |
| 88 | 52 | `file://` URL or a file system path. as sensible: |
| 89 | 53 | only localmatter when operating on a local SQLite DB |
| 90 | -file.For | |
| 91 | -the most part, you want to simply read the [reference material | |
| 92 | -below](#ref)r such a path, | |
| 54 | +file. The same is true when working on a clone done over such a path, | |
| 93 | 55 | except thAsat there are |
| 94 | 56 | |
| 95 | 57 | [sync][sync] with |
| @@ -111,109 +73,31 @@ | ||
| 111 | 73 | |
| 112 | 74 | The SSH client command defaults to “`ssh -e none -T`” on most |
| 113 | 75 | This is unavoidable because those check-ins are already written durably |
| 114 | -t user(s)](#a). Both are | |
| 115 | -(#l), [ticket](#q), and [forum](#5)(#7)(#g)[j](#j)[o](#o)[r](#r)[z](#z)(#h)[m](#m)[n](#n)[c](#c)(#k)[p](#p)[t](#t)[w](#w)(#d)[e](#e)[i](#i)group"></a>Login Groups | |
| 76 | +to [the local Fossil block chain][bc]. Changing a check-in’s user name | |
| 77 | +during sync would require rewriting parts of that block chain, which | |
| 78 | +then means it isn’t actually a “sync”. Either the local and | |
| 79 | +remote clones would be different or the check-in IDs would change as the | |
| 80 | +artifacts get rewritten. That in turn means all references to the old | |
| 81 | +IDs in check-in comments, wiki articles, forum posts, tic | |
| 116 | 82 | |
| 117 | -The Admin → Login-Groups UI feature and its corresponding [`login-group` | |
| 118 | -command][lg] solve a common problem with Fossil: you’ve created multiple | |
| 119 | -repositories that some set of users all need access to, those users all | |
| 120 | -have the same access level on all of these shared repositories, and you | |
| 121 | -don’t want to redundantly configure the user set for each repository. | |
| 83 | +This does mean that anyone with check-in rights on your repository can | |
| 84 | +impersonate any Fossil user in those check-ins. They check in their work | |
| 85 | +under any name they like locally, then upon sync, those names a. Be careful who ybc]: ../blockchain.md | |
| 86 | +prise you is that usns over | |
| 87 | +`http[s]://` URLs, and [thauthor”.][japi]. | |
| 122 | 88 | |
| 123 | -This feature ties changes to the “`user`” table in one repo to that in | |
| 124 | -one or more other repos. With this configured, you get a new choice on | |
| 125 | -the user edit screen, offering to make changes specific to the one | |
| 126 | -repository only or to apply it to all others in the login group as well. | |
| 89 | +User caps *do not* affect operations done on a local repo opened via a | |
| 90 | +`file://` URL or a file system path. as sensible: | |
| 91 | +only localmatter when operating on a local SQLite DB | |
| 92 | +file. The same is true when working on a clone done over such a path, | |
| 93 | +except thAsat there are | |
| 94 | + | |
| 95 | +[sync][sync] with | |
| 96 | +effectively | |
| 97 | +both sides of the sync. | |
| 127 | 98 | |
| 128 | -A user can log into one repo in a login group only if that user has an | |
| 129 | -entry in that repo’s user table. That is, setting up a login group | |
| 130 | -doesn’t automatically transfer all user accounts from the joined repo to | |
| 131 | -the joining repo. Only when a user exists by name in both repos will | |
| 132 | -that user be able to share credentials across the repos. | |
| 133 | - | |
| 134 | -Login groups can have names, allowing one “master” repo to host multiple | |
| 135 | -subsets of its users to other repos. | |
| 136 | - | |
| 137 | -Trust in login groups is transitive within a single server. If repo C | |
| 138 | -joined repo B and repo B joined A, changes in C’s user table affect both | |
| 139 | -A and B, if you tell Fossil that the change applies to all repos in the | |
| 140 | -login group. | |
| 141 | - | |
| 142 | -[](#defuser) (#group)all of | |
| 143 | -the user cap checks in Fossil are on its web interfaces only. | |
| 144 | - | |
| 145 | -TODO: Why then can I not `/xfer` my local repo contents to a remote repo | |
| 146 | -without logging in?/sync.wiki | |
| 147 | - | |
| 148 | -## <a name="ref"></a>Capability Reference | |
| 149 | - | |
| 150 | -This section documents each currently-defined usery character | |
| 151 | -in more detail than the brief summary on the [user capability “key” | |
| 152 | -page](/setup_ucap_list). Each entry begins with the capability letter | |
| 153 | -used in the Fossil user editor followed by the C code’s name for that | |
| 154 | -cap within the `FossilUserPerms` object. | |
| 155 | - | |
| 156 | -The [mnemonics][mn] given here vary from obviously-correct to *post | |
| 157 | -facto* rationalizations to the outright fanciful. To [some | |
| 158 | -extent](#choices), this is unavoidable. | |
| 159 | - | |
| 160 | -* <a name="a"></a>**a (Admin)** — Admin users have *all* of the capabilities | |
| 161 | - below except for [setup](#s). See [Admin vs. Setup][avs] for a more | |
| 162 | - nuanced discussion. Mnemonic: **a**dministrate. | |
| 163 | - | |
| 164 | -* b"></a>**b (Attach)** — Add attachments to wiki articles or tickets. | |
| 165 | - Mnemonics: **b**ind, **b**utton, **b**ond, or **b**olt. | |
| 166 | - | |
| 167 | -* <a name="c"></a>**c (ApndTkt)** — Append comments to existing tickets. | |
| 168 | - Mnemonic: **c**omment. | |
| 169 | - | |
| 170 | -* <a name="d"></a>**d (Delete)** — Delete wiki articles or tickets. Mnemonic: | |
| 171 | - **d**elete. | |
| 172 | - | |
| 173 | -* <a name="e"></a>**e (RdAddr)** — View [personal identifying information][pii] | |
| 174 | - (PII) about other users such as email addresses. Mnemonics: show | |
| 175 | - **e**mail addresses; or **E**urope, home of [GDPR][gdpr]. | |
| 176 | - | |
| 177 | -* <a name="f"></a>**f (NewWiki)** — Create new wiki articles. Mnemonic: | |
| 178 | - **f**ast, English translation of the Hawaiian word [*wiki*][wnh]. | |
| 179 | - | |
| 180 | -* <a name="g"></a>**g (Clone)** — Clone the repository. Note that this is | |
| 181 | - distinct from [check-out capability, **o**](#o). Mnemonic: **g**et. | |
| 182 | - | |
| 183 | -* <a name="h"></a>**h (Hyperlink)** — Get hyperlinks in generated HTML which link | |
| 184 | - you to other parts of the repository. This capability exists and is | |
| 185 | - disabled by default for/` URLs, and [the JSON API to [prevent bots from | |
| 186 | - wandering around aimlessly][bot] in the site’s hyperlink web, | |
| 187 | - chewing up server resources to little good purpose. Mnemonic: | |
| 188 | - **h**yperlink. | |
| 189 | - | |
| 190 | -* <a name="i"></a>**i (Write)** — Check changes into the repository. Note that | |
| 191 | - a lack of this capability does not prevent you from checking changes | |
| 192 | - into your local clone, only from syncing those changes up to the | |
| 193 | - parent repo, and then [only over HTTP](#webonly). Granting this | |
| 194 | - capability also grants **o (Read)**. Mnemonic: check **i**n | |
| 195 | - changes. | |
| 196 | - | |
| 197 | -* <a name="j"></a>**j (RdWiki)** — View wiki articles. Mnemonic: in**j**est | |
| 198 | - page content. (All right, you critics, you do better, then.) | |
| 199 | - | |
| 200 | -* <a name="k"></a>**k (WrWiki)** — Edit wiki articles. Granting this | |
| 201 | - capability also grants **j (RdWiki)** and **m (ApndWiki)**, but it | |
| 202 | - does *not* grant **f (NewWiki)**! Mnemonic: **k**ontribute. | |
| 203 | - | |
| 204 | -* <a name="l"></a>**l (ModWiki)** — Moderate [wiki article appends](#m). Appends | |
| 205 | - do not get saved permamently to the receiving repo’s block chain | |
| 206 | - until some user (one with this cap or [Setup cap](#s)) approves it. | |
| 207 | - Mnemonic: a**l**low. | |
| 208 | - | |
| 209 | -* <a name="m"></a>**m (ApndWiki)** — Append content to existing wiki articles. | |
| 210 | - Mmnemonics: a**m**end or **m**odify. | |
| 211 | - | |
| 212 | -* <a name="n"></a>**n (NewTkt)** — File new tickets. Mnemonic: **n**ew ticket. | |
| 213 | - | |
| 214 | -* <a name="o"></a>**o (Read)** — Read repository content from a remote | |
| 215 | - Fossil instance over HTTP. This | |
| 216 | - reading data from a local | |
| 217 | - web interfaces | |
| 218 | - | |
| 219 | - of whether your user | |
| 99 | +What may surHowever, iadmin users are [subordinate to the setup | |
| 100 | +user(s)][avsp]. Both are superior to all other usersWhen you create a new repository, Fossil creates only one user account | |
| 101 | +named after your e defaults areall of the above plus the | |
| 102 | +The SSH client commandlocalIt from low-status visitors | |
| 103 | +see |
| --- a/www/caps/index.md | |
| +++ b/www/caps/index.md | |
| @@ -1,60 +1,4 @@ | |
| 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] different capabilities. We |
| 13 | explain how we came to assign each character [below](#impl).when working on a clone done over such a path, |
| 14 | except thAsat there are |
| 15 | |
| 16 | [sync][sy[sync]: /help?cmd=synchen |
| 17 | |
| 18 | local clone, |
| 19 | |
| 20 | is on the local file system. If you can log into the remote system over |
| 21 | on that |
| 22 | , it isfor `file://` URLs. |
| 23 | |
| 24 | All��. |
| 25 | Yssh-command` |
| 26 | selocal fileadd |
| 27 | ie without cap checks. The SSH client defaults to “`ssh |
| 28 | -e none -T`” on most platforms, except on Windows where it defaults |
| 29 | ,n’t do this |
| 30 | withBecause both mechanisms work on local repos, the checks for capabilities |
| 31 | for |
| 32 | such URLs can never return “false,” because you are the [**S(#group)ecause you are the [**Setup**][s] |
| 33 | user on both sides of the conversation. Such check |
| 34 | effect ddd][d][e][e][i][i]**: delete,cmdcmdcmdcmdcmdcmdyour user is effectivelyuser][apsu] on both sides of the SSH connection. |
| 35 | |
| 36 | Fossil reuses the HTTP-based [sync protocol][sp] in both cases above, |
| 37 | tunnelling HTTP through an OS pipe or through SSH (FIXME?), but because |
| 38 | are |
| 39 | done against your effective Setup user on the other repo, the check only |
| 40 | has an cmd(../embeddeddoc.wiki) |
| 41 | Yssh-command` |
| 42 | setticap]: https://f repo |
| 43 | that’s mais://fossil-scm.org/home/file?ci=8813ae91a699ac73&name=src%2Fmain.c&ln=2632-2637User caps only affect Fossil’s [UI pages][wp], remote operations over |
| 44 | `http[s]://` URLs, and [the JSON API][japi]. |
| 45 | |
| 46 | User caps *do not* affect operations done on a local repo opened via a |
| 47 | `file://` URL or a file system path. as sensible: |
| 48 | only localmatter when operating on a local SQLite DB |
| 49 | file. The same is tr(#u)e over such a path, |
| 50 | except th(#v)local fileadding a |
| 51 | [**Se capability |
| 52 | namenamenamenamenamenamenamenamenamenamecap]. |
| 53 | |
| 54 | The SSH client command defaults to “`ssh -e none -T`” on most |
| 55 | platforms except Windows where it defaults to “`plink -ssh -T`”. |
| 56 | Yssh-command` |
| 57 | setticap]: https://fossil-scm.org/home/file?ci=8813ae91a699ac73&name=src%2Fmain.c&ln=2632-263eadding a |
| 58 | [**Se capability |
| 59 | namenamenamenamenamenamenamenamenamenamecap]. |
| 60 | |
| @@ -82,14 +26,32 @@ | |
| 82 | on that |
| 83 | , it isfor `file://` URLs. |
| 84 | |
| 85 | Ad [the JSON API][japi]. |
| 86 | |
| 87 | User caps *do not* affect operations done on a local repo opened via a |
| 88 | `file://` URL or a file system path. as sensible: |
| 89 | only localmatter when operating on a local SQLite DB |
| 90 | file.For |
| 91 | the most part, you want to simply read the [reference material |
| 92 | below](#ref)r such a path, |
| 93 | except thAsat there are |
| 94 | |
| 95 | [sync][sync] with |
| @@ -111,109 +73,31 @@ | |
| 111 | |
| 112 | The SSH client command defaults to “`ssh -e none -T`” on most |
| 113 | This is unavoidable because those check-ins are already written durably |
| 114 | t user(s)](#a). Both are |
| 115 | (#l), [ticket](#q), and [forum](#5)(#7)(#g)[j](#j)[o](#o)[r](#r)[z](#z)(#h)[m](#m)[n](#n)[c](#c)(#k)[p](#p)[t](#t)[w](#w)(#d)[e](#e)[i](#i)group"></a>Login Groups |
| 116 | |
| 117 | The Admin → Login-Groups UI feature and its corresponding [`login-group` |
| 118 | command][lg] solve a common problem with Fossil: you’ve created multiple |
| 119 | repositories that some set of users all need access to, those users all |
| 120 | have the same access level on all of these shared repositories, and you |
| 121 | don’t want to redundantly configure the user set for each repository. |
| 122 | |
| 123 | This feature ties changes to the “`user`” table in one repo to that in |
| 124 | one or more other repos. With this configured, you get a new choice on |
| 125 | the user edit screen, offering to make changes specific to the one |
| 126 | repository only or to apply it to all others in the login group as well. |
| 127 | |
| 128 | A user can log into one repo in a login group only if that user has an |
| 129 | entry in that repo’s user table. That is, setting up a login group |
| 130 | doesn’t automatically transfer all user accounts from the joined repo to |
| 131 | the joining repo. Only when a user exists by name in both repos will |
| 132 | that user be able to share credentials across the repos. |
| 133 | |
| 134 | Login groups can have names, allowing one “master” repo to host multiple |
| 135 | subsets of its users to other repos. |
| 136 | |
| 137 | Trust in login groups is transitive within a single server. If repo C |
| 138 | joined repo B and repo B joined A, changes in C’s user table affect both |
| 139 | A and B, if you tell Fossil that the change applies to all repos in the |
| 140 | login group. |
| 141 | |
| 142 | [](#defuser) (#group)all of |
| 143 | the user cap checks in Fossil are on its web interfaces only. |
| 144 | |
| 145 | TODO: Why then can I not `/xfer` my local repo contents to a remote repo |
| 146 | without logging in?/sync.wiki |
| 147 | |
| 148 | ## <a name="ref"></a>Capability Reference |
| 149 | |
| 150 | This section documents each currently-defined usery character |
| 151 | in more detail than the brief summary on the [user capability “key” |
| 152 | page](/setup_ucap_list). Each entry begins with the capability letter |
| 153 | used in the Fossil user editor followed by the C code’s name for that |
| 154 | cap within the `FossilUserPerms` object. |
| 155 | |
| 156 | The [mnemonics][mn] given here vary from obviously-correct to *post |
| 157 | facto* rationalizations to the outright fanciful. To [some |
| 158 | extent](#choices), this is unavoidable. |
| 159 | |
| 160 | * <a name="a"></a>**a (Admin)** — Admin users have *all* of the capabilities |
| 161 | below except for [setup](#s). See [Admin vs. Setup][avs] for a more |
| 162 | nuanced discussion. Mnemonic: **a**dministrate. |
| 163 | |
| 164 | * b"></a>**b (Attach)** — Add attachments to wiki articles or tickets. |
| 165 | Mnemonics: **b**ind, **b**utton, **b**ond, or **b**olt. |
| 166 | |
| 167 | * <a name="c"></a>**c (ApndTkt)** — Append comments to existing tickets. |
| 168 | Mnemonic: **c**omment. |
| 169 | |
| 170 | * <a name="d"></a>**d (Delete)** — Delete wiki articles or tickets. Mnemonic: |
| 171 | **d**elete. |
| 172 | |
| 173 | * <a name="e"></a>**e (RdAddr)** — View [personal identifying information][pii] |
| 174 | (PII) about other users such as email addresses. Mnemonics: show |
| 175 | **e**mail addresses; or **E**urope, home of [GDPR][gdpr]. |
| 176 | |
| 177 | * <a name="f"></a>**f (NewWiki)** — Create new wiki articles. Mnemonic: |
| 178 | **f**ast, English translation of the Hawaiian word [*wiki*][wnh]. |
| 179 | |
| 180 | * <a name="g"></a>**g (Clone)** — Clone the repository. Note that this is |
| 181 | distinct from [check-out capability, **o**](#o). Mnemonic: **g**et. |
| 182 | |
| 183 | * <a name="h"></a>**h (Hyperlink)** — Get hyperlinks in generated HTML which link |
| 184 | you to other parts of the repository. This capability exists and is |
| 185 | disabled by default for/` URLs, and [the JSON API to [prevent bots from |
| 186 | wandering around aimlessly][bot] in the site’s hyperlink web, |
| 187 | chewing up server resources to little good purpose. Mnemonic: |
| 188 | **h**yperlink. |
| 189 | |
| 190 | * <a name="i"></a>**i (Write)** — Check changes into the repository. Note that |
| 191 | a lack of this capability does not prevent you from checking changes |
| 192 | into your local clone, only from syncing those changes up to the |
| 193 | parent repo, and then [only over HTTP](#webonly). Granting this |
| 194 | capability also grants **o (Read)**. Mnemonic: check **i**n |
| 195 | changes. |
| 196 | |
| 197 | * <a name="j"></a>**j (RdWiki)** — View wiki articles. Mnemonic: in**j**est |
| 198 | page content. (All right, you critics, you do better, then.) |
| 199 | |
| 200 | * <a name="k"></a>**k (WrWiki)** — Edit wiki articles. Granting this |
| 201 | capability also grants **j (RdWiki)** and **m (ApndWiki)**, but it |
| 202 | does *not* grant **f (NewWiki)**! Mnemonic: **k**ontribute. |
| 203 | |
| 204 | * <a name="l"></a>**l (ModWiki)** — Moderate [wiki article appends](#m). Appends |
| 205 | do not get saved permamently to the receiving repo’s block chain |
| 206 | until some user (one with this cap or [Setup cap](#s)) approves it. |
| 207 | Mnemonic: a**l**low. |
| 208 | |
| 209 | * <a name="m"></a>**m (ApndWiki)** — Append content to existing wiki articles. |
| 210 | Mmnemonics: a**m**end or **m**odify. |
| 211 | |
| 212 | * <a name="n"></a>**n (NewTkt)** — File new tickets. Mnemonic: **n**ew ticket. |
| 213 | |
| 214 | * <a name="o"></a>**o (Read)** — Read repository content from a remote |
| 215 | Fossil instance over HTTP. This |
| 216 | reading data from a local |
| 217 | web interfaces |
| 218 | |
| 219 | of whether your user |
| --- a/www/caps/index.md | |
| +++ b/www/caps/index.md | |
| @@ -1,60 +1,4 @@ | |
| 1 | local fileadding a |
| 2 | [**Se capability |
| 3 | namenamenamenamenamenamenamenamenamenamecap]. |
| 4 | |
| @@ -82,14 +26,32 @@ | |
| 26 | on that |
| 27 | , it isfor `file://` URLs. |
| 28 | |
| 29 | All��. |
| 30 | Yssh-command` |
| 31 | selocal fileadd |
| 32 | ie without cap checks. The SSH client defaults to “`ssh |
| 33 | -e none -T`” on most platforms, except on Windows where it defaults |
| 34 | ,n’t do this |
| 35 | withBecause both mechanisms work on local repos, the checks for capabilities |
| 36 | for |
| 37 | such URLs can never return “false,” because you are the [**Setup**][s] |
| 38 | user on both sides of the conversation. Such check |
| 39 | effect ddd][d][e][e][i][i]**: delete,cmdcmdcmdcmdcmdcmdyour user is effectivelyuser][apsu] on both sides of the SSH connection. |
| 40 | |
| 41 | Fossil reuses the HTTP-based [sync protocol][sp] in both cases above, |
| 42 | tunnelling HTTP through an OS pipe or through SSH (FIXME?), but because |
| 43 | are |
| 44 | done against your effective Setup user on the other repo, the check only |
| 45 | has an cmd(../embeddeddoc.wiki) |
| 46 | Yssh-command` |
| 47 | setticap]: https://f repo |
| 48 | that’s mais://fossil-scm.org/home/file?ci=8813ae91a699ac73&name=src%2Fmain.c&ln=2632-2637User caps only affect Fossil’s [UI pages][wp], remote operations over |
| 49 | `http[s]://` URLs, and [the JSON API][japi]. |
| 50 | |
| 51 | User caps *do not* affect operations done on a local repo opened via a |
| 52 | `file://` URL or a file system path. as sensible: |
| 53 | only localmatter when operating on a local SQLite DB |
| 54 | file. The same is true when working on a clone done over such a path, |
| 55 | except thAsat there are |
| 56 | |
| 57 | [sync][sync] with |
| @@ -111,109 +73,31 @@ | |
| 73 | |
| 74 | The SSH client command defaults to “`ssh -e none -T`” on most |
| 75 | This is unavoidable because those check-ins are already written durably |
| 76 | to [the local Fossil block chain][bc]. Changing a check-in’s user name |
| 77 | during sync would require rewriting parts of that block chain, which |
| 78 | then means it isn’t actually a “sync”. Either the local and |
| 79 | remote clones would be different or the check-in IDs would change as the |
| 80 | artifacts get rewritten. That in turn means all references to the old |
| 81 | IDs in check-in comments, wiki articles, forum posts, tic |
| 82 | |
| 83 | This does mean that anyone with check-in rights on your repository can |
| 84 | impersonate any Fossil user in those check-ins. They check in their work |
| 85 | under any name they like locally, then upon sync, those names a. Be careful who ybc]: ../blockchain.md |
| 86 | prise you is that usns over |
| 87 | `http[s]://` URLs, and [thauthor”.][japi]. |
| 88 | |
| 89 | User caps *do not* affect operations done on a local repo opened via a |
| 90 | `file://` URL or a file system path. as sensible: |
| 91 | only localmatter when operating on a local SQLite DB |
| 92 | file. The same is true when working on a clone done over such a path, |
| 93 | except thAsat there are |
| 94 | |
| 95 | [sync][sync] with |
| 96 | effectively |
| 97 | both sides of the sync. |
| 98 | |
| 99 | What may surHowever, iadmin users are [subordinate to the setup |
| 100 | user(s)][avsp]. Both are superior to all other usersWhen you create a new repository, Fossil creates only one user account |
| 101 | named after your e defaults areall of the above plus the |
| 102 | The SSH client commandlocalIt from low-status visitors |
| 103 | see |
| --- a/www/caps/login-groups.md | ||
| +++ b/www/caps/login-groups.md | ||
| @@ -0,0 +1,6 @@ | ||
| 1 | +# Login Groups | |
| 2 | + | |
| 3 | +The Admin → Login-Groups UI feature and its corresponding [`login-groet of users all need access to, those users all | |
| 4 | +have the same access level on all oconfigure the us. With this configureIf repo C | |
| 5 | +joined repo B and repo B joined A, changes in C’s user table affect both | |
| 6 | +A and B, if you tell Fossil that the change applilogin group |
| --- a/www/caps/login-groups.md | |
| +++ b/www/caps/login-groups.md | |
| @@ -0,0 +1,6 @@ | |
| --- a/www/caps/login-groups.md | |
| +++ b/www/caps/login-groups.md | |
| @@ -0,0 +1,6 @@ | |
| 1 | # Login Groups |
| 2 | |
| 3 | The Admin → Login-Groups UI feature and its corresponding [`login-groet of users all need access to, those users all |
| 4 | have the same access level on all oconfigure the us. With this configureIf repo C |
| 5 | joined repo B and repo B joined A, changes in C’s user table affect both |
| 6 | A and B, if you tell Fossil that the change applilogin group |
+90
| --- a/www/caps/ref.html | ||
| +++ b/www/caps/ref.html | ||
| @@ -0,0 +1,90 @@ | ||
| 1 | +<div class='fossil This | |
| 2 | + letter was assigned by default to Developer in repos created with | |
| 3 | + Fossil 2.10 or earlier, but it has no effect in current or past | |
| 4 | +. Mnemonic: | |
| 5 | + repository contentits durable blockchain nature“key� page</a>’Dele<div class='fossil This<div cMnemonic: <b>d</b>ele“nobody�’<div class='fossil This | |
| 6 | + letter was assigned by default to Developer in repos created with | |
| 7 | + Fossil 2.10 or earlier, but it has no effect in current or past | |
| 8 | +. Mnemonic: | |
| 9 | + repository contentits durable blockchain natureis | |
| 10 | + letter was assigned“key”’ated with | |
| 11 | + Fossil 2.10 or earlier, but it has no effect in current or past | |
| 12 | +. Mnemonic: | |
| 13 | + repository contentits durable bl<div class='fossil This | |
| 14 | + letter was assigned by default to Developer in repos created with | |
| 15 | + Fossil 2.10 or earlier, but it has no effect in current or p’’“anonymous�“reader�“developer�“x�div class='fossil This | |
| 16 | + letter was assigned by default to Developer in repos created wit='fossil“hand over.�’“�iv class='fossil This | |
| 17 | + letter was assigned by default to Developer in repos created with | |
| 18 | + Fossil 2.10 or earlier, but it has no effect in curre letter�“Approve�’“I’�’ urrent or past | |
| 19 | +. Mnemonic: | |
| 20 | + repository. | |
| 21 | + Fossil | |
| 22 | + Setup</a> for a more€™â€™â€œanonymous� | |
| 23 | + letter was assigned by default to Developer in repos created with | |
| 24 | + Fossil 2.10 or earlier, but it has no effect in current or past | |
| 25 | +. Mnemonic: | |
| 26 | + repository contentits durable blockchain nature“key� page</a>’Dele<div class='fossil This<div cMnemonic: <b>d</b>ele“nobody�’<div class='fossil This | |
| 27 | + letter was assigned by default to Developer in repos created with | |
| 28 | + Fossil 2.10 or earlier, but it has no effect in current or past | |
| 29 | +. Mnemonic: | |
| 30 | + repository contentits durable blockchain natureis | |
| 31 | + letter was assigned“key”’ated with | |
| 32 | + Fossil 2.10 or earlier, but it has no effect in current or past | |
| 33 | +. Mnemonic: | |
| 34 | + repository contentits durable bl<div class='fossil This | |
| 35 | + letter was assigned by default to Developer in repos created with | |
| 36 | + Fossil 2.10 or earlier, but it has no effect in current or p’’“anonymous�“reader�“developer�“x�div class='fossil This | |
| 37 | + letter was assigned by default to Developer in repos created wit='fossil“hand over.�’“�iv class='fossil This | |
| 38 | + letter was assigned by default to Developer in repos created with | |
| 39 | + Fossil 2.10 or earlier, but it has no effect in curre letter�“Approve�’“I’�’ urrent or past | |
| 40 | +. Mnemonic: | |
| 41 | + repositorytter was assigned by default to Developer in repos created with | |
| 42 | + Fossil 2.10 or earlier, but it has no effect in current or p’’“anonymous�“reader�“developer�“x�div class='fossil This | |
| 43 | + letter was assigned by default to Developer in repos created wit='fossil“hand over.�’“�iv cl er was assigned by default to Developer in repos created with | |
| 44 | + Fossil 2.10 or earlier, but it has no effect in curre letterâ€�“Approveâ€�’“I’â€�’“nobody”’ <div class='fossil This | |
| 45 | + letter was assigned by default to Developer in repos created with | |
| 46 | + Fossil 2.10 or earlier, but it has no effect in current or past | |
| 47 | +. Mnemonic: | |
| 48 | + repository c | |
| 49 | + ’ os created with | |
| 50 | + Fossil 2.10 or earlier, but it has no effect in current or past | |
| 51 | +. Mnemonic: | |
| 52 | + repository contentits durable blockchain nature“keyâ€� page</a>’Dele<div class='fossil This<div cMnemonic: <b>d</b>ele“nobodyâ€�’<’ ’“anonymous”div class='fossil This | |
| 53 | + letter was assigned by default to Developer in repos created with | |
| 54 | + Fossil 2.10 or earlier, but it has no effect in current or past | |
| 55 | +. Mnemonic: | |
| 56 | + repository contentits durable blockchain nature“keyâ€� page</a>’Dele<div class='fossil This<div cMnemonic: <b>d</b>ele“nobodyâ€�’i“reader” “developer” “x”�om� “hand over.” ’ “” “”“Approve”’“I’” ’ <div class='fossil This | |
| 57 | + letter was assigned by default to Developer in repos created with | |
| 58 | + Fossil 2.10 or earlier, but it has no effect in current or past | |
| 59 | +. Mnemonic: | |
| 60 | + repository contentits durable blockchain nature“key� page</a>’Dele<div class='fossil This<div cMnemonic: <b>d</b>ele“nobody�’<div class='fossil This | |
| 61 | + letter was assigned by default to Developer in repos created with | |
| 62 | + Fossil 2.10 or earlier, but it has no effect in current or past | |
| 63 | +. Mnemonic: | |
| 64 | + repository contentits durable blockchain natureis | |
| 65 | + letter was assigned“key”’ated with | |
| 66 | + Fossil 2.10 or earlier, but it has no effect in current or past | |
| 67 | +. Mnemonic: | |
| 68 | + repository contentits durable bl<div class='fossil This | |
| 69 | + letter was assigned by default to Developer in repos created with | |
| 70 | + Fossil 2.10 or earlier, but it has no effect in current or p’’“anonymous�“reader�“developer�“x�div class='fossil This | |
| 71 | + letter was assigned by default to Developer in repos created wit='fossil“hand over.�’“�iv class='fossil This | |
| 72 | + letter was assigned by default to Developer in repos created with | |
| 73 | + Fossil 2.10 or earlier, but it has no effect in curre letter�“Approve�’“I’�’ urrent or past | |
| 74 | +. Mnemonic: | |
| 75 | + repositorytter was assigned by default to Developer in repos created with | |
| 76 | + Fossil 2.10 or earlier, but it has no effect in current or p’’“anonymous�“reader�“developer�“x�div class='fossil This | |
| 77 | + letter was assigned by default to Developer in repos created wit='fossil“hand over.�’“�iv cl er was assigned by default to Developer in repos created with | |
| 78 | + Fossil 2.10 or earlier, but it has no effect in curre letterâ€�“Approveâ€�’“I’â€�’“nobody”’ <div class='fossil This | |
| 79 | + letter was assigned by default to Developer in repos created with | |
| 80 | + Fossil 2.10 or earlier, but it has no effect in current or past | |
| 81 | +. Mnemonic: | |
| 82 | + repository c | |
| 83 | + ’ os created with | |
| 84 | + Fossil 2.10 or earlier, but it has no effect in current or past | |
| 85 | +. Mnemonic: | |
| 86 | + repository contentits durable blockchain nature“keyâ€� page</a>’Dele<div class='fossil This<div cMnemonic: <b>d</b>ele“nobodyâ€�’<’ ’“anonymous”div class='fossil This | |
| 87 | + letter was assigned by default to Developer in repos created with | |
| 88 | + Fossil 2.10 or earlier, but it has no effect in current or past | |
| 89 | +. Mnemonic: | |
| 90 | + repository contentits durable blockchain nature“keyâ€� page</a>’Dele<div class='fossil This<div cMnemonic: <b>d</b>ele“nobodyâ€�’i“reader” “developer” “x”�om� “hand over.” ’ “” “”“Approve”’“I’” ’ S Mnemonic:r, but it has no ef |
| --- a/www/caps/ref.html | |
| +++ b/www/caps/ref.html | |
| @@ -0,0 +1,90 @@ | |
| --- a/www/caps/ref.html | |
| +++ b/www/caps/ref.html | |
| @@ -0,0 +1,90 @@ | |
| 1 | <div class='fossil This |
| 2 | letter was assigned by default to Developer in repos created with |
| 3 | Fossil 2.10 or earlier, but it has no effect in current or past |
| 4 | . Mnemonic: |
| 5 | repository contentits durable blockchain nature“key� page</a>’Dele<div class='fossil This<div cMnemonic: <b>d</b>ele“nobody�’<div class='fossil This |
| 6 | letter was assigned by default to Developer in repos created with |
| 7 | Fossil 2.10 or earlier, but it has no effect in current or past |
| 8 | . Mnemonic: |
| 9 | repository contentits durable blockchain natureis |
| 10 | letter was assigned“key”’ated with |
| 11 | Fossil 2.10 or earlier, but it has no effect in current or past |
| 12 | . Mnemonic: |
| 13 | repository contentits durable bl<div class='fossil This |
| 14 | letter was assigned by default to Developer in repos created with |
| 15 | Fossil 2.10 or earlier, but it has no effect in current or p’’“anonymous�“reader�“developer�“x�div class='fossil This |
| 16 | letter was assigned by default to Developer in repos created wit='fossil“hand over.�’“�iv class='fossil This |
| 17 | letter was assigned by default to Developer in repos created with |
| 18 | Fossil 2.10 or earlier, but it has no effect in curre letter�“Approve�’“I’�’ urrent or past |
| 19 | . Mnemonic: |
| 20 | repository. |
| 21 | Fossil |
| 22 | Setup</a> for a more€™â€™â€œanonymous� |
| 23 | letter was assigned by default to Developer in repos created with |
| 24 | Fossil 2.10 or earlier, but it has no effect in current or past |
| 25 | . Mnemonic: |
| 26 | repository contentits durable blockchain nature“key� page</a>’Dele<div class='fossil This<div cMnemonic: <b>d</b>ele“nobody�’<div class='fossil This |
| 27 | letter was assigned by default to Developer in repos created with |
| 28 | Fossil 2.10 or earlier, but it has no effect in current or past |
| 29 | . Mnemonic: |
| 30 | repository contentits durable blockchain natureis |
| 31 | letter was assigned“key”’ated with |
| 32 | Fossil 2.10 or earlier, but it has no effect in current or past |
| 33 | . Mnemonic: |
| 34 | repository contentits durable bl<div class='fossil This |
| 35 | letter was assigned by default to Developer in repos created with |
| 36 | Fossil 2.10 or earlier, but it has no effect in current or p’’“anonymous�“reader�“developer�“x�div class='fossil This |
| 37 | letter was assigned by default to Developer in repos created wit='fossil“hand over.�’“�iv class='fossil This |
| 38 | letter was assigned by default to Developer in repos created with |
| 39 | Fossil 2.10 or earlier, but it has no effect in curre letter�“Approve�’“I’�’ urrent or past |
| 40 | . Mnemonic: |
| 41 | repositorytter was assigned by default to Developer in repos created with |
| 42 | Fossil 2.10 or earlier, but it has no effect in current or p’’“anonymous�“reader�“developer�“x�div class='fossil This |
| 43 | letter was assigned by default to Developer in repos created wit='fossil“hand over.�’“�iv cl er was assigned by default to Developer in repos created with |
| 44 | Fossil 2.10 or earlier, but it has no effect in curre letterâ€�“Approveâ€�’“I’â€�’“nobody”’ <div class='fossil This |
| 45 | letter was assigned by default to Developer in repos created with |
| 46 | Fossil 2.10 or earlier, but it has no effect in current or past |
| 47 | . Mnemonic: |
| 48 | repository c |
| 49 | ’ os created with |
| 50 | Fossil 2.10 or earlier, but it has no effect in current or past |
| 51 | . Mnemonic: |
| 52 | repository contentits durable blockchain nature“keyâ€� page</a>’Dele<div class='fossil This<div cMnemonic: <b>d</b>ele“nobodyâ€�’<’ ’“anonymous”div class='fossil This |
| 53 | letter was assigned by default to Developer in repos created with |
| 54 | Fossil 2.10 or earlier, but it has no effect in current or past |
| 55 | . Mnemonic: |
| 56 | repository contentits durable blockchain nature“keyâ€� page</a>’Dele<div class='fossil This<div cMnemonic: <b>d</b>ele“nobodyâ€�’i“reader” “developer” “x”�om� “hand over.” ’ “” “”“Approve”’“I’” ’ <div class='fossil This |
| 57 | letter was assigned by default to Developer in repos created with |
| 58 | Fossil 2.10 or earlier, but it has no effect in current or past |
| 59 | . Mnemonic: |
| 60 | repository contentits durable blockchain nature“key� page</a>’Dele<div class='fossil This<div cMnemonic: <b>d</b>ele“nobody�’<div class='fossil This |
| 61 | letter was assigned by default to Developer in repos created with |
| 62 | Fossil 2.10 or earlier, but it has no effect in current or past |
| 63 | . Mnemonic: |
| 64 | repository contentits durable blockchain natureis |
| 65 | letter was assigned“key”’ated with |
| 66 | Fossil 2.10 or earlier, but it has no effect in current or past |
| 67 | . Mnemonic: |
| 68 | repository contentits durable bl<div class='fossil This |
| 69 | letter was assigned by default to Developer in repos created with |
| 70 | Fossil 2.10 or earlier, but it has no effect in current or p’’“anonymous�“reader�“developer�“x�div class='fossil This |
| 71 | letter was assigned by default to Developer in repos created wit='fossil“hand over.�’“�iv class='fossil This |
| 72 | letter was assigned by default to Developer in repos created with |
| 73 | Fossil 2.10 or earlier, but it has no effect in curre letter�“Approve�’“I’�’ urrent or past |
| 74 | . Mnemonic: |
| 75 | repositorytter was assigned by default to Developer in repos created with |
| 76 | Fossil 2.10 or earlier, but it has no effect in current or p’’“anonymous�“reader�“developer�“x�div class='fossil This |
| 77 | letter was assigned by default to Developer in repos created wit='fossil“hand over.�’“�iv cl er was assigned by default to Developer in repos created with |
| 78 | Fossil 2.10 or earlier, but it has no effect in curre letterâ€�“Approveâ€�’“I’â€�’“nobody”’ <div class='fossil This |
| 79 | letter was assigned by default to Developer in repos created with |
| 80 | Fossil 2.10 or earlier, but it has no effect in current or past |
| 81 | . Mnemonic: |
| 82 | repository c |
| 83 | ’ os created with |
| 84 | Fossil 2.10 or earlier, but it has no effect in current or past |
| 85 | . Mnemonic: |
| 86 | repository contentits durable blockchain nature“keyâ€� page</a>’Dele<div class='fossil This<div cMnemonic: <b>d</b>ele“nobodyâ€�’<’ ’“anonymous”div class='fossil This |
| 87 | letter was assigned by default to Developer in repos created with |
| 88 | Fossil 2.10 or earlier, but it has no effect in current or past |
| 89 | . Mnemonic: |
| 90 | repository contentits durable blockchain nature“keyâ€� page</a>’Dele<div class='fossil This<div cMnemonic: <b>d</b>ele“nobodyâ€�’i“reader” “developer” “x”�om� “hand over.” ’ “” “”“Approve”’“I’” ’ S Mnemonic:r, but it has no ef |
+4
-2
| --- www/mkindex.tcl | ||
| +++ www/mkindex.tcl | ||
| @@ -9,20 +9,22 @@ | ||
| 9 | 9 | set doclist { |
| 10 | 10 | aboutcgi.wiki {How CGI Works In Fossil} |
| 11 | 11 | aboutdownload.wiki {How The Download Page Works} |
| 12 | 12 | adding_code.wiki {Adding New Features To Fossil} |
| 13 | 13 | adding_code.wiki {Hacking Fossil} |
| 14 | - admin-v-setup.md {The Differences Between the Setup and Admin User Capabilities} | |
| 15 | 14 | alerts.md {Email Alerts And Notifications} |
| 16 | 15 | antibot.wiki {Defense against Spiders and Bots} |
| 17 | 16 | backoffice.md {The "Backoffice" mechanism of Fossil} |
| 18 | 17 | blame.wiki {The Annotate/Blame Algorithm Of Fossil} |
| 19 | 18 | blockchain.md {Fossil As Blockchain} |
| 20 | 19 | branching.wiki {Branching, Forking, Merging, and Tagging} |
| 21 | 20 | bugtheory.wiki {Bug Tracking In Fossil} |
| 22 | 21 | build.wiki {Compiling and Installing Fossil} |
| 23 | - capabilities.md {Administering User Capabilities} | |
| 22 | + caps/ {Administering User Capabilities} | |
| 23 | + caps/admin-v-setup.md {Differences Between Setup and Admin Users} | |
| 24 | + caps/login-groups.md {Differences Between Setup and Admin Users} | |
| 25 | + caps/ref.html {User Capability Reference} | |
| 24 | 26 | cgi.wiki {CGI Script Configuration Options} |
| 25 | 27 | changes.wiki {Fossil Changelog} |
| 26 | 28 | checkin_names.wiki {Check-in And Version Names} |
| 27 | 29 | checkin.wiki {Check-in Checklist} |
| 28 | 30 | childprojects.wiki {Child Projects} |
| 29 | 31 |
| --- www/mkindex.tcl | |
| +++ www/mkindex.tcl | |
| @@ -9,20 +9,22 @@ | |
| 9 | set doclist { |
| 10 | aboutcgi.wiki {How CGI Works In Fossil} |
| 11 | aboutdownload.wiki {How The Download Page Works} |
| 12 | adding_code.wiki {Adding New Features To Fossil} |
| 13 | adding_code.wiki {Hacking Fossil} |
| 14 | admin-v-setup.md {The Differences Between the Setup and Admin User Capabilities} |
| 15 | alerts.md {Email Alerts And Notifications} |
| 16 | antibot.wiki {Defense against Spiders and Bots} |
| 17 | backoffice.md {The "Backoffice" mechanism of Fossil} |
| 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 |
| --- www/mkindex.tcl | |
| +++ www/mkindex.tcl | |
| @@ -9,20 +9,22 @@ | |
| 9 | set doclist { |
| 10 | aboutcgi.wiki {How CGI Works In Fossil} |
| 11 | aboutdownload.wiki {How The Download Page Works} |
| 12 | adding_code.wiki {Adding New Features To Fossil} |
| 13 | adding_code.wiki {Hacking Fossil} |
| 14 | alerts.md {Email Alerts And Notifications} |
| 15 | antibot.wiki {Defense against Spiders and Bots} |
| 16 | backoffice.md {The "Backoffice" mechanism of Fossil} |
| 17 | blame.wiki {The Annotate/Blame Algorithm Of Fossil} |
| 18 | blockchain.md {Fossil As Blockchain} |
| 19 | branching.wiki {Branching, Forking, Merging, and Tagging} |
| 20 | bugtheory.wiki {Bug Tracking In Fossil} |
| 21 | build.wiki {Compiling and Installing Fossil} |
| 22 | caps/ {Administering User Capabilities} |
| 23 | caps/admin-v-setup.md {Differences Between Setup and Admin Users} |
| 24 | caps/login-groups.md {Differences Between Setup and Admin Users} |
| 25 | caps/ref.html {User Capability Reference} |
| 26 | cgi.wiki {CGI Script Configuration Options} |
| 27 | changes.wiki {Fossil Changelog} |
| 28 | checkin_names.wiki {Check-in And Version Names} |
| 29 | checkin.wiki {Check-in Checklist} |
| 30 | childprojects.wiki {Child Projects} |
| 31 |
+16
-7
| --- www/permutedindex.html | ||
| +++ www/permutedindex.html | ||
| @@ -23,11 +23,13 @@ | ||
| 23 | 23 | <li><a href="fiveminutes.wiki">5 Minutes as a Single User — Up and Running in</a></li> |
| 24 | 24 | <li><a href="fossil-from-msvc.wiki">2010 IDE — Integrating Fossil in the Microsoft Express</a></li> |
| 25 | 25 | <li><a href="tech_overview.wiki"><b>A Technical Overview Of The Design And Implementation Of Fossil</b></a></li> |
| 26 | 26 | <li><a href="serverext.wiki"><b>Adding Extensions To A Fossil Server Using CGI Scripts</b></a></li> |
| 27 | 27 | <li><a href="adding_code.wiki"><b>Adding New Features To Fossil</b></a></li> |
| 28 | -<li><a href="admin-v-setup.md">Admin User Capabilities — The Differences Between the Setup and</a></li> | |
| 28 | +<li><a href="caps/admin-v-setup.md">Admin Users — Differences Between Setup and</a></li> | |
| 29 | +<li><a href="caps/login-groups.md">Admin Users — Differences Between Setup and</a></li> | |
| 30 | +<li><a href="caps/"><b>Administering User Capabilities</b></a></li> | |
| 29 | 31 | <li><a href="copyright-release.html">Agreement — Contributor License</a></li> |
| 30 | 32 | <li><a href="alerts.md">Alerts And Notifications — Email</a></li> |
| 31 | 33 | <li><a href="delta_encoder_algorithm.wiki">Algorithm — Fossil Delta Encoding</a></li> |
| 32 | 34 | <li><a href="blame.wiki">Algorithm Of Fossil — The Annotate/Blame</a></li> |
| 33 | 35 | <li><a href="blame.wiki">Annotate/Blame Algorithm Of Fossil — The</a></li> |
| @@ -35,19 +37,21 @@ | ||
| 35 | 37 | <li><a href="faq.wiki">Asked Questions — Frequently</a></li> |
| 36 | 38 | <li><a href="password.wiki">Authentication — Password Management And</a></li> |
| 37 | 39 | <li><a href="backoffice.md">Backoffice mechanism of Fossil — The</a></li> |
| 38 | 40 | <li><a href="fossil_prompt.wiki">Bash Prompt — Fossilized</a></li> |
| 39 | 41 | <li><a href="whyusefossil.wiki"><b>Benefits Of Version Control</b></a></li> |
| 42 | +<li><a href="caps/admin-v-setup.md">Between Setup and Admin Users — Differences</a></li> | |
| 43 | +<li><a href="caps/login-groups.md">Between Setup and Admin Users — Differences</a></li> | |
| 40 | 44 | <li><a href="hashpolicy.wiki">Between SHA1 and SHA3-256 — Hash Policy: Choosing</a></li> |
| 41 | -<li><a href="admin-v-setup.md">Between the Setup and Admin User Capabilities — The Differences</a></li> | |
| 42 | 45 | <li><a href="blockchain.md">Blockchain — Fossil As</a></li> |
| 43 | 46 | <li><a href="antibot.wiki">Bots — Defense against Spiders and</a></li> |
| 44 | 47 | <li><a href="private.wiki">Branches — Creating, Syncing, and Deleting Private</a></li> |
| 45 | 48 | <li><a href="branching.wiki"><b>Branching, Forking, Merging, and Tagging</b></a></li> |
| 46 | 49 | <li><a href="bugtheory.wiki"><b>Bug Tracking In Fossil</b></a></li> |
| 47 | 50 | <li><a href="makefile.wiki">Build Process — The Fossil</a></li> |
| 48 | -<li><a href="admin-v-setup.md">Capabilities — The Differences Between the Setup and Admin User</a></li> | |
| 51 | +<li><a href="caps/">Capabilities — Administering User</a></li> | |
| 52 | +<li><a href="caps/ref.html">Capability Reference — User</a></li> | |
| 49 | 53 | <li><a href="cgi.wiki"><b>CGI Script Configuration Options</b></a></li> |
| 50 | 54 | <li><a href="serverext.wiki">CGI Scripts — Adding Extensions To A Fossil Server Using</a></li> |
| 51 | 55 | <li><a href="serverext.wiki"><b>CGI Server Extensions</b></a></li> |
| 52 | 56 | <li><a href="aboutcgi.wiki">CGI Works In Fossil — How</a></li> |
| 53 | 57 | <li><a href="changes.wiki">Changelog — Fossil</a></li> |
| @@ -86,11 +90,12 @@ | ||
| 86 | 90 | <li><a href="private.wiki">Deleting Private Branches — Creating, Syncing, and</a></li> |
| 87 | 91 | <li><a href="delta_encoder_algorithm.wiki">Delta Encoding Algorithm — Fossil</a></li> |
| 88 | 92 | <li><a href="delta_format.wiki">Delta Format — Fossil</a></li> |
| 89 | 93 | <li><a href="tech_overview.wiki">Design And Implementation Of Fossil — A Technical Overview Of The</a></li> |
| 90 | 94 | <li><a href="theory1.wiki">Design Of The Fossil DVCS — Thoughts On The</a></li> |
| 91 | -<li><a href="admin-v-setup.md">Differences Between the Setup and Admin User Capabilities — The</a></li> | |
| 95 | +<li><a href="caps/admin-v-setup.md"><b>Differences Between Setup and Admin Users</b></a></li> | |
| 96 | +<li><a href="caps/login-groups.md"><b>Differences Between Setup and Admin Users</b></a></li> | |
| 92 | 97 | <li><a href="embeddeddoc.wiki">Documentation — Embedded Project</a></li> |
| 93 | 98 | <li><a href="contribute.wiki">Documentation To The Fossil Project — Contributing Code or</a></li> |
| 94 | 99 | <li><a href="aboutdownload.wiki">Download Page Works — How The</a></li> |
| 95 | 100 | <li><a href="theory1.wiki">DVCS — Thoughts On The Design Of The Fossil</a></li> |
| 96 | 101 | <li><a href="quotes.wiki">DVCSes in General — Quotes: What People Are Saying About Fossil, Git, and</a></li> |
| @@ -215,10 +220,11 @@ | ||
| 215 | 220 | <li><a href="tls-nginx.md"><b>Proxying Fossil via HTTPS with nginx</b></a></li> |
| 216 | 221 | <li><a href="faq.wiki">Questions — Frequently Asked</a></li> |
| 217 | 222 | <li><a href="qandc.wiki"><b>Questions And Criticisms</b></a></li> |
| 218 | 223 | <li><a href="quickstart.wiki">Quick Start Guide — Fossil</a></li> |
| 219 | 224 | <li><a href="quotes.wiki"><b>Quotes: What People Are Saying About Fossil, Git, and DVCSes in General</b></a></li> |
| 225 | +<li><a href="caps/ref.html">Reference — User Capability</a></li> | |
| 220 | 226 | <li><a href="image-format-vs-repo-size.md">Repo Size — Image Format vs Fossil</a></li> |
| 221 | 227 | <li><a href="selfhost.wiki">Repositories — Fossil Self Hosting</a></li> |
| 222 | 228 | <li><a href="encryptedrepos.wiki">Repositories — How To Use Encrypted</a></li> |
| 223 | 229 | <li><a href="newrepo.wiki">Repository — How To Create A New Fossil</a></li> |
| 224 | 230 | <li><a href="selfcheck.wiki">Repository Integrity Self Checks — Fossil</a></li> |
| @@ -236,11 +242,12 @@ | ||
| 236 | 242 | <li><a href="selfhost.wiki">Self Hosting Repositories — Fossil</a></li> |
| 237 | 243 | <li><a href="server/">Server — How To Configure A Fossil</a></li> |
| 238 | 244 | <li><a href="serverext.wiki">Server Extensions — CGI</a></li> |
| 239 | 245 | <li><a href="serverext.wiki">Server Using CGI Scripts — Adding Extensions To A Fossil</a></li> |
| 240 | 246 | <li><a href="settings.wiki">Settings — Fossil</a></li> |
| 241 | -<li><a href="admin-v-setup.md">Setup and Admin User Capabilities — The Differences Between the</a></li> | |
| 247 | +<li><a href="caps/admin-v-setup.md">Setup and Admin Users — Differences Between</a></li> | |
| 248 | +<li><a href="caps/login-groups.md">Setup and Admin Users — Differences Between</a></li> | |
| 242 | 249 | <li><a href="hashpolicy.wiki">SHA1 and SHA3-256 — Hash Policy: Choosing Between</a></li> |
| 243 | 250 | <li><a href="hashpolicy.wiki">SHA3-256 — Hash Policy: Choosing Between SHA1 and</a></li> |
| 244 | 251 | <li><a href="shunning.wiki"><b>Shunning: Deleting Content From Fossil</b></a></li> |
| 245 | 252 | <li><a href="fiveminutes.wiki">Single User — Up and Running in 5 Minutes as a</a></li> |
| 246 | 253 | <li><a href="../../../sitemap"><b>Site Map</b></a></li> |
| @@ -263,11 +270,10 @@ | ||
| 263 | 270 | <li><a href="../test/release-checklist.wiki">Testing Checklist — Pre-Release</a></li> |
| 264 | 271 | <li><a href="th1.md">TH1 Scripting Language — The</a></li> |
| 265 | 272 | <li><a href="backoffice.md"><b>The "Backoffice" mechanism of Fossil</b></a></li> |
| 266 | 273 | <li><a href="blame.wiki"><b>The Annotate/Blame Algorithm Of Fossil</b></a></li> |
| 267 | 274 | <li><a href="defcsp.md"><b>The Default Content Security Policy</b></a></li> |
| 268 | -<li><a href="admin-v-setup.md"><b>The Differences Between the Setup and Admin User Capabilities</b></a></li> | |
| 269 | 275 | <li><a href="makefile.wiki"><b>The Fossil Build Process</b></a></li> |
| 270 | 276 | <li><a href="sync.wiki"><b>The Fossil Sync Protocol</b></a></li> |
| 271 | 277 | <li><a href="tickets.wiki"><b>The Fossil Ticket System</b></a></li> |
| 272 | 278 | <li><a href="webui.wiki"><b>The Fossil Web Interface</b></a></li> |
| 273 | 279 | <li><a href="th1.md"><b>The TH1 Scripting Language</b></a></li> |
| @@ -281,11 +287,14 @@ | ||
| 281 | 287 | <li><a href="bugtheory.wiki">Tracking In Fossil — Bug</a></li> |
| 282 | 288 | <li><a href="unvers.wiki"><b>Unversioned Files</b></a></li> |
| 283 | 289 | <li><a href="fiveminutes.wiki"><b>Up and Running in 5 Minutes as a Single User</b></a></li> |
| 284 | 290 | <li><a href="hints.wiki">Usage Hints — Fossil Tips And</a></li> |
| 285 | 291 | <li><a href="fiveminutes.wiki">User — Up and Running in 5 Minutes as a Single</a></li> |
| 286 | -<li><a href="admin-v-setup.md">User Capabilities — The Differences Between the Setup and Admin</a></li> | |
| 292 | +<li><a href="caps/">User Capabilities — Administering</a></li> | |
| 293 | +<li><a href="caps/ref.html"><b>User Capability Reference</b></a></li> | |
| 294 | +<li><a href="caps/admin-v-setup.md">Users — Differences Between Setup and Admin</a></li> | |
| 295 | +<li><a href="caps/login-groups.md">Users — Differences Between Setup and Admin</a></li> | |
| 287 | 296 | <li><a href="serverext.wiki">Using CGI Scripts — Adding Extensions To A Fossil Server</a></li> |
| 288 | 297 | <li><a href="ssl.wiki"><b>Using SSL with Fossil</b></a></li> |
| 289 | 298 | <li><a href="env-opts.md">Variables and Global Options — Environment</a></li> |
| 290 | 299 | <li><a href="whyusefossil.wiki">Version Control — Benefits Of</a></li> |
| 291 | 300 | <li><a href="checkin_names.wiki">Version Names — Check-in And</a></li> |
| 292 | 301 |
| --- www/permutedindex.html | |
| +++ www/permutedindex.html | |
| @@ -23,11 +23,13 @@ | |
| 23 | <li><a href="fiveminutes.wiki">5 Minutes as a Single User — Up and Running in</a></li> |
| 24 | <li><a href="fossil-from-msvc.wiki">2010 IDE — Integrating Fossil in the Microsoft Express</a></li> |
| 25 | <li><a href="tech_overview.wiki"><b>A Technical Overview Of The Design And Implementation Of Fossil</b></a></li> |
| 26 | <li><a href="serverext.wiki"><b>Adding Extensions To A Fossil Server Using CGI Scripts</b></a></li> |
| 27 | <li><a href="adding_code.wiki"><b>Adding New Features To Fossil</b></a></li> |
| 28 | <li><a href="admin-v-setup.md">Admin User Capabilities — The Differences Between the Setup and</a></li> |
| 29 | <li><a href="copyright-release.html">Agreement — Contributor License</a></li> |
| 30 | <li><a href="alerts.md">Alerts And Notifications — Email</a></li> |
| 31 | <li><a href="delta_encoder_algorithm.wiki">Algorithm — Fossil Delta Encoding</a></li> |
| 32 | <li><a href="blame.wiki">Algorithm Of Fossil — The Annotate/Blame</a></li> |
| 33 | <li><a href="blame.wiki">Annotate/Blame Algorithm Of Fossil — The</a></li> |
| @@ -35,19 +37,21 @@ | |
| 35 | <li><a href="faq.wiki">Asked Questions — Frequently</a></li> |
| 36 | <li><a href="password.wiki">Authentication — Password Management And</a></li> |
| 37 | <li><a href="backoffice.md">Backoffice mechanism of Fossil — The</a></li> |
| 38 | <li><a href="fossil_prompt.wiki">Bash Prompt — Fossilized</a></li> |
| 39 | <li><a href="whyusefossil.wiki"><b>Benefits Of Version Control</b></a></li> |
| 40 | <li><a href="hashpolicy.wiki">Between SHA1 and SHA3-256 — Hash Policy: Choosing</a></li> |
| 41 | <li><a href="admin-v-setup.md">Between the Setup and Admin User Capabilities — The Differences</a></li> |
| 42 | <li><a href="blockchain.md">Blockchain — Fossil As</a></li> |
| 43 | <li><a href="antibot.wiki">Bots — Defense against Spiders and</a></li> |
| 44 | <li><a href="private.wiki">Branches — Creating, Syncing, and Deleting Private</a></li> |
| 45 | <li><a href="branching.wiki"><b>Branching, Forking, Merging, and Tagging</b></a></li> |
| 46 | <li><a href="bugtheory.wiki"><b>Bug Tracking In Fossil</b></a></li> |
| 47 | <li><a href="makefile.wiki">Build Process — The Fossil</a></li> |
| 48 | <li><a href="admin-v-setup.md">Capabilities — The Differences Between the Setup and Admin User</a></li> |
| 49 | <li><a href="cgi.wiki"><b>CGI Script Configuration Options</b></a></li> |
| 50 | <li><a href="serverext.wiki">CGI Scripts — Adding Extensions To A Fossil Server Using</a></li> |
| 51 | <li><a href="serverext.wiki"><b>CGI Server Extensions</b></a></li> |
| 52 | <li><a href="aboutcgi.wiki">CGI Works In Fossil — How</a></li> |
| 53 | <li><a href="changes.wiki">Changelog — Fossil</a></li> |
| @@ -86,11 +90,12 @@ | |
| 86 | <li><a href="private.wiki">Deleting Private Branches — Creating, Syncing, and</a></li> |
| 87 | <li><a href="delta_encoder_algorithm.wiki">Delta Encoding Algorithm — Fossil</a></li> |
| 88 | <li><a href="delta_format.wiki">Delta Format — Fossil</a></li> |
| 89 | <li><a href="tech_overview.wiki">Design And Implementation Of Fossil — A Technical Overview Of The</a></li> |
| 90 | <li><a href="theory1.wiki">Design Of The Fossil DVCS — Thoughts On The</a></li> |
| 91 | <li><a href="admin-v-setup.md">Differences Between the Setup and Admin User Capabilities — The</a></li> |
| 92 | <li><a href="embeddeddoc.wiki">Documentation — Embedded Project</a></li> |
| 93 | <li><a href="contribute.wiki">Documentation To The Fossil Project — Contributing Code or</a></li> |
| 94 | <li><a href="aboutdownload.wiki">Download Page Works — How The</a></li> |
| 95 | <li><a href="theory1.wiki">DVCS — Thoughts On The Design Of The Fossil</a></li> |
| 96 | <li><a href="quotes.wiki">DVCSes in General — Quotes: What People Are Saying About Fossil, Git, and</a></li> |
| @@ -215,10 +220,11 @@ | |
| 215 | <li><a href="tls-nginx.md"><b>Proxying Fossil via HTTPS with nginx</b></a></li> |
| 216 | <li><a href="faq.wiki">Questions — Frequently Asked</a></li> |
| 217 | <li><a href="qandc.wiki"><b>Questions And Criticisms</b></a></li> |
| 218 | <li><a href="quickstart.wiki">Quick Start Guide — Fossil</a></li> |
| 219 | <li><a href="quotes.wiki"><b>Quotes: What People Are Saying About Fossil, Git, and DVCSes in General</b></a></li> |
| 220 | <li><a href="image-format-vs-repo-size.md">Repo Size — Image Format vs Fossil</a></li> |
| 221 | <li><a href="selfhost.wiki">Repositories — Fossil Self Hosting</a></li> |
| 222 | <li><a href="encryptedrepos.wiki">Repositories — How To Use Encrypted</a></li> |
| 223 | <li><a href="newrepo.wiki">Repository — How To Create A New Fossil</a></li> |
| 224 | <li><a href="selfcheck.wiki">Repository Integrity Self Checks — Fossil</a></li> |
| @@ -236,11 +242,12 @@ | |
| 236 | <li><a href="selfhost.wiki">Self Hosting Repositories — Fossil</a></li> |
| 237 | <li><a href="server/">Server — How To Configure A Fossil</a></li> |
| 238 | <li><a href="serverext.wiki">Server Extensions — CGI</a></li> |
| 239 | <li><a href="serverext.wiki">Server Using CGI Scripts — Adding Extensions To A Fossil</a></li> |
| 240 | <li><a href="settings.wiki">Settings — Fossil</a></li> |
| 241 | <li><a href="admin-v-setup.md">Setup and Admin User Capabilities — The Differences Between the</a></li> |
| 242 | <li><a href="hashpolicy.wiki">SHA1 and SHA3-256 — Hash Policy: Choosing Between</a></li> |
| 243 | <li><a href="hashpolicy.wiki">SHA3-256 — Hash Policy: Choosing Between SHA1 and</a></li> |
| 244 | <li><a href="shunning.wiki"><b>Shunning: Deleting Content From Fossil</b></a></li> |
| 245 | <li><a href="fiveminutes.wiki">Single User — Up and Running in 5 Minutes as a</a></li> |
| 246 | <li><a href="../../../sitemap"><b>Site Map</b></a></li> |
| @@ -263,11 +270,10 @@ | |
| 263 | <li><a href="../test/release-checklist.wiki">Testing Checklist — Pre-Release</a></li> |
| 264 | <li><a href="th1.md">TH1 Scripting Language — The</a></li> |
| 265 | <li><a href="backoffice.md"><b>The "Backoffice" mechanism of Fossil</b></a></li> |
| 266 | <li><a href="blame.wiki"><b>The Annotate/Blame Algorithm Of Fossil</b></a></li> |
| 267 | <li><a href="defcsp.md"><b>The Default Content Security Policy</b></a></li> |
| 268 | <li><a href="admin-v-setup.md"><b>The Differences Between the Setup and Admin User Capabilities</b></a></li> |
| 269 | <li><a href="makefile.wiki"><b>The Fossil Build Process</b></a></li> |
| 270 | <li><a href="sync.wiki"><b>The Fossil Sync Protocol</b></a></li> |
| 271 | <li><a href="tickets.wiki"><b>The Fossil Ticket System</b></a></li> |
| 272 | <li><a href="webui.wiki"><b>The Fossil Web Interface</b></a></li> |
| 273 | <li><a href="th1.md"><b>The TH1 Scripting Language</b></a></li> |
| @@ -281,11 +287,14 @@ | |
| 281 | <li><a href="bugtheory.wiki">Tracking In Fossil — Bug</a></li> |
| 282 | <li><a href="unvers.wiki"><b>Unversioned Files</b></a></li> |
| 283 | <li><a href="fiveminutes.wiki"><b>Up and Running in 5 Minutes as a Single User</b></a></li> |
| 284 | <li><a href="hints.wiki">Usage Hints — Fossil Tips And</a></li> |
| 285 | <li><a href="fiveminutes.wiki">User — Up and Running in 5 Minutes as a Single</a></li> |
| 286 | <li><a href="admin-v-setup.md">User Capabilities — The Differences Between the Setup and Admin</a></li> |
| 287 | <li><a href="serverext.wiki">Using CGI Scripts — Adding Extensions To A Fossil Server</a></li> |
| 288 | <li><a href="ssl.wiki"><b>Using SSL with Fossil</b></a></li> |
| 289 | <li><a href="env-opts.md">Variables and Global Options — Environment</a></li> |
| 290 | <li><a href="whyusefossil.wiki">Version Control — Benefits Of</a></li> |
| 291 | <li><a href="checkin_names.wiki">Version Names — Check-in And</a></li> |
| 292 |
| --- www/permutedindex.html | |
| +++ www/permutedindex.html | |
| @@ -23,11 +23,13 @@ | |
| 23 | <li><a href="fiveminutes.wiki">5 Minutes as a Single User — Up and Running in</a></li> |
| 24 | <li><a href="fossil-from-msvc.wiki">2010 IDE — Integrating Fossil in the Microsoft Express</a></li> |
| 25 | <li><a href="tech_overview.wiki"><b>A Technical Overview Of The Design And Implementation Of Fossil</b></a></li> |
| 26 | <li><a href="serverext.wiki"><b>Adding Extensions To A Fossil Server Using CGI Scripts</b></a></li> |
| 27 | <li><a href="adding_code.wiki"><b>Adding New Features To Fossil</b></a></li> |
| 28 | <li><a href="caps/admin-v-setup.md">Admin Users — Differences Between Setup and</a></li> |
| 29 | <li><a href="caps/login-groups.md">Admin Users — Differences Between Setup and</a></li> |
| 30 | <li><a href="caps/"><b>Administering User Capabilities</b></a></li> |
| 31 | <li><a href="copyright-release.html">Agreement — Contributor License</a></li> |
| 32 | <li><a href="alerts.md">Alerts And Notifications — Email</a></li> |
| 33 | <li><a href="delta_encoder_algorithm.wiki">Algorithm — Fossil Delta Encoding</a></li> |
| 34 | <li><a href="blame.wiki">Algorithm Of Fossil — The Annotate/Blame</a></li> |
| 35 | <li><a href="blame.wiki">Annotate/Blame Algorithm Of Fossil — The</a></li> |
| @@ -35,19 +37,21 @@ | |
| 37 | <li><a href="faq.wiki">Asked Questions — Frequently</a></li> |
| 38 | <li><a href="password.wiki">Authentication — Password Management And</a></li> |
| 39 | <li><a href="backoffice.md">Backoffice mechanism of Fossil — The</a></li> |
| 40 | <li><a href="fossil_prompt.wiki">Bash Prompt — Fossilized</a></li> |
| 41 | <li><a href="whyusefossil.wiki"><b>Benefits Of Version Control</b></a></li> |
| 42 | <li><a href="caps/admin-v-setup.md">Between Setup and Admin Users — Differences</a></li> |
| 43 | <li><a href="caps/login-groups.md">Between Setup and Admin Users — Differences</a></li> |
| 44 | <li><a href="hashpolicy.wiki">Between SHA1 and SHA3-256 — Hash Policy: Choosing</a></li> |
| 45 | <li><a href="blockchain.md">Blockchain — Fossil As</a></li> |
| 46 | <li><a href="antibot.wiki">Bots — Defense against Spiders and</a></li> |
| 47 | <li><a href="private.wiki">Branches — Creating, Syncing, and Deleting Private</a></li> |
| 48 | <li><a href="branching.wiki"><b>Branching, Forking, Merging, and Tagging</b></a></li> |
| 49 | <li><a href="bugtheory.wiki"><b>Bug Tracking In Fossil</b></a></li> |
| 50 | <li><a href="makefile.wiki">Build Process — The Fossil</a></li> |
| 51 | <li><a href="caps/">Capabilities — Administering User</a></li> |
| 52 | <li><a href="caps/ref.html">Capability Reference — User</a></li> |
| 53 | <li><a href="cgi.wiki"><b>CGI Script Configuration Options</b></a></li> |
| 54 | <li><a href="serverext.wiki">CGI Scripts — Adding Extensions To A Fossil Server Using</a></li> |
| 55 | <li><a href="serverext.wiki"><b>CGI Server Extensions</b></a></li> |
| 56 | <li><a href="aboutcgi.wiki">CGI Works In Fossil — How</a></li> |
| 57 | <li><a href="changes.wiki">Changelog — Fossil</a></li> |
| @@ -86,11 +90,12 @@ | |
| 90 | <li><a href="private.wiki">Deleting Private Branches — Creating, Syncing, and</a></li> |
| 91 | <li><a href="delta_encoder_algorithm.wiki">Delta Encoding Algorithm — Fossil</a></li> |
| 92 | <li><a href="delta_format.wiki">Delta Format — Fossil</a></li> |
| 93 | <li><a href="tech_overview.wiki">Design And Implementation Of Fossil — A Technical Overview Of The</a></li> |
| 94 | <li><a href="theory1.wiki">Design Of The Fossil DVCS — Thoughts On The</a></li> |
| 95 | <li><a href="caps/admin-v-setup.md"><b>Differences Between Setup and Admin Users</b></a></li> |
| 96 | <li><a href="caps/login-groups.md"><b>Differences Between Setup and Admin Users</b></a></li> |
| 97 | <li><a href="embeddeddoc.wiki">Documentation — Embedded Project</a></li> |
| 98 | <li><a href="contribute.wiki">Documentation To The Fossil Project — Contributing Code or</a></li> |
| 99 | <li><a href="aboutdownload.wiki">Download Page Works — How The</a></li> |
| 100 | <li><a href="theory1.wiki">DVCS — Thoughts On The Design Of The Fossil</a></li> |
| 101 | <li><a href="quotes.wiki">DVCSes in General — Quotes: What People Are Saying About Fossil, Git, and</a></li> |
| @@ -215,10 +220,11 @@ | |
| 220 | <li><a href="tls-nginx.md"><b>Proxying Fossil via HTTPS with nginx</b></a></li> |
| 221 | <li><a href="faq.wiki">Questions — Frequently Asked</a></li> |
| 222 | <li><a href="qandc.wiki"><b>Questions And Criticisms</b></a></li> |
| 223 | <li><a href="quickstart.wiki">Quick Start Guide — Fossil</a></li> |
| 224 | <li><a href="quotes.wiki"><b>Quotes: What People Are Saying About Fossil, Git, and DVCSes in General</b></a></li> |
| 225 | <li><a href="caps/ref.html">Reference — User Capability</a></li> |
| 226 | <li><a href="image-format-vs-repo-size.md">Repo Size — Image Format vs Fossil</a></li> |
| 227 | <li><a href="selfhost.wiki">Repositories — Fossil Self Hosting</a></li> |
| 228 | <li><a href="encryptedrepos.wiki">Repositories — How To Use Encrypted</a></li> |
| 229 | <li><a href="newrepo.wiki">Repository — How To Create A New Fossil</a></li> |
| 230 | <li><a href="selfcheck.wiki">Repository Integrity Self Checks — Fossil</a></li> |
| @@ -236,11 +242,12 @@ | |
| 242 | <li><a href="selfhost.wiki">Self Hosting Repositories — Fossil</a></li> |
| 243 | <li><a href="server/">Server — How To Configure A Fossil</a></li> |
| 244 | <li><a href="serverext.wiki">Server Extensions — CGI</a></li> |
| 245 | <li><a href="serverext.wiki">Server Using CGI Scripts — Adding Extensions To A Fossil</a></li> |
| 246 | <li><a href="settings.wiki">Settings — Fossil</a></li> |
| 247 | <li><a href="caps/admin-v-setup.md">Setup and Admin Users — Differences Between</a></li> |
| 248 | <li><a href="caps/login-groups.md">Setup and Admin Users — Differences Between</a></li> |
| 249 | <li><a href="hashpolicy.wiki">SHA1 and SHA3-256 — Hash Policy: Choosing Between</a></li> |
| 250 | <li><a href="hashpolicy.wiki">SHA3-256 — Hash Policy: Choosing Between SHA1 and</a></li> |
| 251 | <li><a href="shunning.wiki"><b>Shunning: Deleting Content From Fossil</b></a></li> |
| 252 | <li><a href="fiveminutes.wiki">Single User — Up and Running in 5 Minutes as a</a></li> |
| 253 | <li><a href="../../../sitemap"><b>Site Map</b></a></li> |
| @@ -263,11 +270,10 @@ | |
| 270 | <li><a href="../test/release-checklist.wiki">Testing Checklist — Pre-Release</a></li> |
| 271 | <li><a href="th1.md">TH1 Scripting Language — The</a></li> |
| 272 | <li><a href="backoffice.md"><b>The "Backoffice" mechanism of Fossil</b></a></li> |
| 273 | <li><a href="blame.wiki"><b>The Annotate/Blame Algorithm Of Fossil</b></a></li> |
| 274 | <li><a href="defcsp.md"><b>The Default Content Security Policy</b></a></li> |
| 275 | <li><a href="makefile.wiki"><b>The Fossil Build Process</b></a></li> |
| 276 | <li><a href="sync.wiki"><b>The Fossil Sync Protocol</b></a></li> |
| 277 | <li><a href="tickets.wiki"><b>The Fossil Ticket System</b></a></li> |
| 278 | <li><a href="webui.wiki"><b>The Fossil Web Interface</b></a></li> |
| 279 | <li><a href="th1.md"><b>The TH1 Scripting Language</b></a></li> |
| @@ -281,11 +287,14 @@ | |
| 287 | <li><a href="bugtheory.wiki">Tracking In Fossil — Bug</a></li> |
| 288 | <li><a href="unvers.wiki"><b>Unversioned Files</b></a></li> |
| 289 | <li><a href="fiveminutes.wiki"><b>Up and Running in 5 Minutes as a Single User</b></a></li> |
| 290 | <li><a href="hints.wiki">Usage Hints — Fossil Tips And</a></li> |
| 291 | <li><a href="fiveminutes.wiki">User — Up and Running in 5 Minutes as a Single</a></li> |
| 292 | <li><a href="caps/">User Capabilities — Administering</a></li> |
| 293 | <li><a href="caps/ref.html"><b>User Capability Reference</b></a></li> |
| 294 | <li><a href="caps/admin-v-setup.md">Users — Differences Between Setup and Admin</a></li> |
| 295 | <li><a href="caps/login-groups.md">Users — Differences Between Setup and Admin</a></li> |
| 296 | <li><a href="serverext.wiki">Using CGI Scripts — Adding Extensions To A Fossil Server</a></li> |
| 297 | <li><a href="ssl.wiki"><b>Using SSL with Fossil</b></a></li> |
| 298 | <li><a href="env-opts.md">Variables and Global Options — Environment</a></li> |
| 299 | <li><a href="whyusefossil.wiki">Version Control — Benefits Of</a></li> |
| 300 | <li><a href="checkin_names.wiki">Version Names — Check-in And</a></li> |
| 301 |