Fossil SCM
Removed all references to "Fossil 2.1x" from the docs, excepting the changelog and the hashpolicy doc. The bulk of these were for 2.14 or older — *ten* versions back now! — and there is no reason to suppose such old versions are still in use any more. These notes were justified when they informed users about surprising changes and feature additions, but they now do nothing but clutter the docs. If I am wrong about people being surprised by these things, we still have the changelog, the timeline, and the forum.
Commit
ad47a447c81277763293d99487c4ea4c12b76ff951d4ce18a50acf48f5277b33
Parent
f3cac5259349653…
19 files changed
-6
+3
-3
+1
-1
+2
-4
+5
-6
+2
-3
+10
-12
+4
-3
-3
+4
-4
+3
-3
+3
-3
+11
-11
+1
-2
+1
-4
+2
-2
-6
+3
-4
-2
~
www/alerts.md
~
www/backup.md
~
www/build.wiki
~
www/caps/ref.html
~
www/chat.md
~
www/ckout-workflows.md
~
www/customskin.md
~
www/defcsp.md
~
www/fileedit-page.md
~
www/fossil-v-git.wiki
~
www/gitusers.md
~
www/glossary.md
~
www/javascript.md
~
www/mirrortogithub.md
~
www/server/debian/nginx.md
~
www/server/windows/service.md
~
www/server/windows/stunnel.md
~
www/ssl.wiki
~
www/th1.md
-6
| --- www/alerts.md | ||
| +++ www/alerts.md | ||
| @@ -578,11 +578,10 @@ | ||
| 578 | 578 | There are two new tables in the repository database, starting with |
| 579 | 579 | Fossil 2.7. These tables are not created in new repositories by |
| 580 | 580 | default. The tables only come into existence as needed when email |
| 581 | 581 | alerts are configured and used. |
| 582 | 582 | |
| 583 | - | |
| 584 | 583 | * <b>SUBSCRIBER</b> → |
| 585 | 584 | The subscriber table records the email address for people who |
| 586 | 585 | want to receive email notifications. Each subscriber has a |
| 587 | 586 | `subscriberCode` which is a random 32-byte blob that uniquely |
| 588 | 587 | identifies the subscriber. There are also fields to indicate |
| @@ -598,15 +597,10 @@ | ||
| 598 | 597 | and records timeline entries. In other words, there is one |
| 599 | 598 | row in the EVENT table for each possible timeline entry. The |
| 600 | 599 | PENDING\_ALERT table refers to EVENT table entries for which |
| 601 | 600 | we might need to send alert emails. |
| 602 | 601 | |
| 603 | -There was a third table "EMAIL_BOUNCE" in Fossil versions 2.7 through 2.14. | |
| 604 | -That table was intended to record email bounce history so that | |
| 605 | -subscribers with excessive bounces can be turned off. But that feature | |
| 606 | -was never implemented and the table was removed in Fossil 2.15. | |
| 607 | - | |
| 608 | 602 | As pointed out above, ["subscribers" are distinct from "users"](#uvs). |
| 609 | 603 | The SUBSCRIBER.SUNAME field is the optional linkage between users and |
| 610 | 604 | subscribers. |
| 611 | 605 | |
| 612 | 606 | |
| 613 | 607 |
| --- www/alerts.md | |
| +++ www/alerts.md | |
| @@ -578,11 +578,10 @@ | |
| 578 | There are two new tables in the repository database, starting with |
| 579 | Fossil 2.7. These tables are not created in new repositories by |
| 580 | default. The tables only come into existence as needed when email |
| 581 | alerts are configured and used. |
| 582 | |
| 583 | |
| 584 | * <b>SUBSCRIBER</b> → |
| 585 | The subscriber table records the email address for people who |
| 586 | want to receive email notifications. Each subscriber has a |
| 587 | `subscriberCode` which is a random 32-byte blob that uniquely |
| 588 | identifies the subscriber. There are also fields to indicate |
| @@ -598,15 +597,10 @@ | |
| 598 | and records timeline entries. In other words, there is one |
| 599 | row in the EVENT table for each possible timeline entry. The |
| 600 | PENDING\_ALERT table refers to EVENT table entries for which |
| 601 | we might need to send alert emails. |
| 602 | |
| 603 | There was a third table "EMAIL_BOUNCE" in Fossil versions 2.7 through 2.14. |
| 604 | That table was intended to record email bounce history so that |
| 605 | subscribers with excessive bounces can be turned off. But that feature |
| 606 | was never implemented and the table was removed in Fossil 2.15. |
| 607 | |
| 608 | As pointed out above, ["subscribers" are distinct from "users"](#uvs). |
| 609 | The SUBSCRIBER.SUNAME field is the optional linkage between users and |
| 610 | subscribers. |
| 611 | |
| 612 | |
| 613 |
| --- www/alerts.md | |
| +++ www/alerts.md | |
| @@ -578,11 +578,10 @@ | |
| 578 | There are two new tables in the repository database, starting with |
| 579 | Fossil 2.7. These tables are not created in new repositories by |
| 580 | default. The tables only come into existence as needed when email |
| 581 | alerts are configured and used. |
| 582 | |
| 583 | * <b>SUBSCRIBER</b> → |
| 584 | The subscriber table records the email address for people who |
| 585 | want to receive email notifications. Each subscriber has a |
| 586 | `subscriberCode` which is a random 32-byte blob that uniquely |
| 587 | identifies the subscriber. There are also fields to indicate |
| @@ -598,15 +597,10 @@ | |
| 597 | and records timeline entries. In other words, there is one |
| 598 | row in the EVENT table for each possible timeline entry. The |
| 599 | PENDING\_ALERT table refers to EVENT table entries for which |
| 600 | we might need to send alert emails. |
| 601 | |
| 602 | As pointed out above, ["subscribers" are distinct from "users"](#uvs). |
| 603 | The SUBSCRIBER.SUNAME field is the optional linkage between users and |
| 604 | subscribers. |
| 605 | |
| 606 | |
| 607 |
+3
-3
| --- www/backup.md | ||
| +++ www/backup.md | ||
| @@ -159,13 +159,13 @@ | ||
| 159 | 159 | The first method doesn’t get you a copy of the remote’s |
| 160 | 160 | [private branches][pbr], on purpose. It may also miss other info on the |
| 161 | 161 | remote, such as SQL-level customizations that the sync protocol can’t |
| 162 | 162 | see. (Some [ticket system customization][tkt] schemes rely on this ability, for example.) You can |
| 163 | 163 | solve such problems if you have access to the remote server, which |
| 164 | -allows you to get a SQL-level backup. This requires Fossil 2.12 or | |
| 165 | -newer, which added [the `backup` command][bu] to take care of | |
| 166 | -locking and transaction isolation, allowing the user to safely back up an in-use | |
| 164 | +allows you to get a SQL-level backup by delegating handling of locking | |
| 165 | +and transaction isolation to | |
| 166 | +[the `backup` command][bu], allowing the user to safely back up an in-use | |
| 167 | 167 | repository. |
| 168 | 168 | |
| 169 | 169 | If you have SSH access to the remote server, something like this will work: |
| 170 | 170 | |
| 171 | 171 | ``` shell |
| 172 | 172 |
| --- www/backup.md | |
| +++ www/backup.md | |
| @@ -159,13 +159,13 @@ | |
| 159 | The first method doesn’t get you a copy of the remote’s |
| 160 | [private branches][pbr], on purpose. It may also miss other info on the |
| 161 | remote, such as SQL-level customizations that the sync protocol can’t |
| 162 | see. (Some [ticket system customization][tkt] schemes rely on this ability, for example.) You can |
| 163 | solve such problems if you have access to the remote server, which |
| 164 | allows you to get a SQL-level backup. This requires Fossil 2.12 or |
| 165 | newer, which added [the `backup` command][bu] to take care of |
| 166 | locking and transaction isolation, allowing the user to safely back up an in-use |
| 167 | repository. |
| 168 | |
| 169 | If you have SSH access to the remote server, something like this will work: |
| 170 | |
| 171 | ``` shell |
| 172 |
| --- www/backup.md | |
| +++ www/backup.md | |
| @@ -159,13 +159,13 @@ | |
| 159 | The first method doesn’t get you a copy of the remote’s |
| 160 | [private branches][pbr], on purpose. It may also miss other info on the |
| 161 | remote, such as SQL-level customizations that the sync protocol can’t |
| 162 | see. (Some [ticket system customization][tkt] schemes rely on this ability, for example.) You can |
| 163 | solve such problems if you have access to the remote server, which |
| 164 | allows you to get a SQL-level backup by delegating handling of locking |
| 165 | and transaction isolation to |
| 166 | [the `backup` command][bu], allowing the user to safely back up an in-use |
| 167 | repository. |
| 168 | |
| 169 | If you have SSH access to the remote server, something like this will work: |
| 170 | |
| 171 | ``` shell |
| 172 |
+1
-1
| --- www/build.wiki | ||
| +++ www/build.wiki | ||
| @@ -411,11 +411,11 @@ | ||
| 411 | 411 | |
| 412 | 412 | |
| 413 | 413 | <a id='wasm'></a> |
| 414 | 414 | <h2>8.0 Building WebAssembly Components</h2> |
| 415 | 415 | |
| 416 | -As of version 2.19, fossil uses one component built as | |
| 416 | +Fossil uses one component built as | |
| 417 | 417 | [https://developer.mozilla.org/en-US/docs/WebAssembly | WebAssembly] |
| 418 | 418 | a.k.a. WASM. Because compiling WASM code requires non-trivial |
| 419 | 419 | client-side tooling, the repository includes compiled copies of these |
| 420 | 420 | pieces. Most Fossil hackers should never need to concern themselves |
| 421 | 421 | with the WASM parts, but this section describes how to for those who |
| 422 | 422 |
| --- www/build.wiki | |
| +++ www/build.wiki | |
| @@ -411,11 +411,11 @@ | |
| 411 | |
| 412 | |
| 413 | <a id='wasm'></a> |
| 414 | <h2>8.0 Building WebAssembly Components</h2> |
| 415 | |
| 416 | As of version 2.19, fossil uses one component built as |
| 417 | [https://developer.mozilla.org/en-US/docs/WebAssembly | WebAssembly] |
| 418 | a.k.a. WASM. Because compiling WASM code requires non-trivial |
| 419 | client-side tooling, the repository includes compiled copies of these |
| 420 | pieces. Most Fossil hackers should never need to concern themselves |
| 421 | with the WASM parts, but this section describes how to for those who |
| 422 |
| --- www/build.wiki | |
| +++ www/build.wiki | |
| @@ -411,11 +411,11 @@ | |
| 411 | |
| 412 | |
| 413 | <a id='wasm'></a> |
| 414 | <h2>8.0 Building WebAssembly Components</h2> |
| 415 | |
| 416 | Fossil uses one component built as |
| 417 | [https://developer.mozilla.org/en-US/docs/WebAssembly | WebAssembly] |
| 418 | a.k.a. WASM. Because compiling WASM code requires non-trivial |
| 419 | client-side tooling, the repository includes compiled copies of these |
| 420 | pieces. Most Fossil hackers should never need to concern themselves |
| 421 | with the WASM parts, but this section describes how to for those who |
| 422 |
+2
-4
| --- www/caps/ref.html | ||
| +++ www/caps/ref.html | ||
| @@ -81,14 +81,12 @@ | ||
| 81 | 81 | <th>d</th> |
| 82 | 82 | <th>n/a</th> |
| 83 | 83 | <td> |
| 84 | 84 | Legacy capability letter from Fossil's forebear <a |
| 85 | 85 | href="http://cvstrac.org/">CVSTrac</a>, which has no useful |
| 86 | - meaning in Fossil due to the nature of its durable Merkle tree design. 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 | - versions of Fossil; we recommend that you remove it in case we | |
| 86 | + meaning in Fossil due to the nature of its durable Merkle tree design. | |
| 87 | + We recommend that you remove it in case we | |
| 90 | 88 | ever reuse this letter for another purpose. See <a |
| 91 | 89 | href="https://fossil-scm.org/forum/forumpost/43c78f4bef">this |
| 92 | 90 | post</a> for details. |
| 93 | 91 | </td> |
| 94 | 92 | </tr> |
| 95 | 93 |
| --- www/caps/ref.html | |
| +++ www/caps/ref.html | |
| @@ -81,14 +81,12 @@ | |
| 81 | <th>d</th> |
| 82 | <th>n/a</th> |
| 83 | <td> |
| 84 | Legacy capability letter from Fossil's forebear <a |
| 85 | href="http://cvstrac.org/">CVSTrac</a>, which has no useful |
| 86 | meaning in Fossil due to the nature of its durable Merkle tree design. 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 | versions of Fossil; we recommend that you remove it in case we |
| 90 | ever reuse this letter for another purpose. See <a |
| 91 | href="https://fossil-scm.org/forum/forumpost/43c78f4bef">this |
| 92 | post</a> for details. |
| 93 | </td> |
| 94 | </tr> |
| 95 |
| --- www/caps/ref.html | |
| +++ www/caps/ref.html | |
| @@ -81,14 +81,12 @@ | |
| 81 | <th>d</th> |
| 82 | <th>n/a</th> |
| 83 | <td> |
| 84 | Legacy capability letter from Fossil's forebear <a |
| 85 | href="http://cvstrac.org/">CVSTrac</a>, which has no useful |
| 86 | meaning in Fossil due to the nature of its durable Merkle tree design. |
| 87 | We recommend that you remove it in case we |
| 88 | ever reuse this letter for another purpose. See <a |
| 89 | href="https://fossil-scm.org/forum/forumpost/43c78f4bef">this |
| 90 | post</a> for details. |
| 91 | </td> |
| 92 | </tr> |
| 93 |
+5
-6
| --- www/chat.md | ||
| +++ www/chat.md | ||
| @@ -1,11 +1,10 @@ | ||
| 1 | 1 | # Fossil Chat |
| 2 | 2 | |
| 3 | 3 | ## Introduction |
| 4 | 4 | |
| 5 | -As of version 2.14, | |
| 6 | -Fossil supports a developer chatroom feature. The chatroom provides an | |
| 5 | +Fossil’s developer chatroom feature provides an | |
| 7 | 6 | ephemeral discussion venue for insiders. Design goals include: |
| 8 | 7 | |
| 9 | 8 | * **Simple but functional** → |
| 10 | 9 | Fossil chat is designed to provide a convenient real-time |
| 11 | 10 | communication mechanism for geographically dispersed developers. |
| @@ -62,12 +61,12 @@ | ||
| 62 | 61 | skin includes a "Chat" entry on the menu bar on wide screens for |
| 63 | 62 | people with chat privilege. There is also a "Chat" option on |
| 64 | 63 | the [Sitemap page](/sitemap), which means that chat will appear |
| 65 | 64 | as an option under the hamburger menu for many [skins](./customskin.md). |
| 66 | 65 | |
| 67 | -As of version 2.17, chat messages are subject to [fossil's | |
| 68 | -full range of markdown processing](/md_rules). Because chat messages are | |
| 66 | +Chat messages are subject to [Fossil's | |
| 67 | +full range of Markdown processing](/md_rules). Because chat messages are | |
| 69 | 68 | stored as-is when they arrive from a client, this change applies |
| 70 | 69 | retroactively to messages stored by previous fossil versions. |
| 71 | 70 | |
| 72 | 71 | Files may be sent via chat using the file selection element at the |
| 73 | 72 | bottom of the page. If the desktop environment system supports it, |
| @@ -110,12 +109,12 @@ | ||
| 110 | 109 | |
| 111 | 110 | ### <a id='connection'></a> Who's Online? |
| 112 | 111 | |
| 113 | 112 | Because the chat app has to be able to work over transient CGI-based |
| 114 | 113 | connections, as opposed to a stable socket connection to the server, |
| 115 | -real-time tracking of "who's online" is not feasible. As of version | |
| 116 | -2.17, chat offers an optional feature, toggleable in the settings, | |
| 114 | +real-time tracking of "who's online" is not feasible. | |
| 115 | +Chat offers an optional feature, toggleable in the settings, | |
| 117 | 116 | which can list users who have posted messages in the client's current |
| 118 | 117 | list of loaded messages. This is not the same thing as tracking who's |
| 119 | 118 | online, but it gives an overview of which users have been active most |
| 120 | 119 | recently, noting that "lurkers" (people who post no messages) will not |
| 121 | 120 | show up in that list, nor does the chat infrastructure have a way to |
| 122 | 121 |
| --- www/chat.md | |
| +++ www/chat.md | |
| @@ -1,11 +1,10 @@ | |
| 1 | # Fossil Chat |
| 2 | |
| 3 | ## Introduction |
| 4 | |
| 5 | As of version 2.14, |
| 6 | Fossil supports a developer chatroom feature. The chatroom provides an |
| 7 | ephemeral discussion venue for insiders. Design goals include: |
| 8 | |
| 9 | * **Simple but functional** → |
| 10 | Fossil chat is designed to provide a convenient real-time |
| 11 | communication mechanism for geographically dispersed developers. |
| @@ -62,12 +61,12 @@ | |
| 62 | skin includes a "Chat" entry on the menu bar on wide screens for |
| 63 | people with chat privilege. There is also a "Chat" option on |
| 64 | the [Sitemap page](/sitemap), which means that chat will appear |
| 65 | as an option under the hamburger menu for many [skins](./customskin.md). |
| 66 | |
| 67 | As of version 2.17, chat messages are subject to [fossil's |
| 68 | full range of markdown processing](/md_rules). Because chat messages are |
| 69 | stored as-is when they arrive from a client, this change applies |
| 70 | retroactively to messages stored by previous fossil versions. |
| 71 | |
| 72 | Files may be sent via chat using the file selection element at the |
| 73 | bottom of the page. If the desktop environment system supports it, |
| @@ -110,12 +109,12 @@ | |
| 110 | |
| 111 | ### <a id='connection'></a> Who's Online? |
| 112 | |
| 113 | Because the chat app has to be able to work over transient CGI-based |
| 114 | connections, as opposed to a stable socket connection to the server, |
| 115 | real-time tracking of "who's online" is not feasible. As of version |
| 116 | 2.17, chat offers an optional feature, toggleable in the settings, |
| 117 | which can list users who have posted messages in the client's current |
| 118 | list of loaded messages. This is not the same thing as tracking who's |
| 119 | online, but it gives an overview of which users have been active most |
| 120 | recently, noting that "lurkers" (people who post no messages) will not |
| 121 | show up in that list, nor does the chat infrastructure have a way to |
| 122 |
| --- www/chat.md | |
| +++ www/chat.md | |
| @@ -1,11 +1,10 @@ | |
| 1 | # Fossil Chat |
| 2 | |
| 3 | ## Introduction |
| 4 | |
| 5 | Fossil’s developer chatroom feature provides an |
| 6 | ephemeral discussion venue for insiders. Design goals include: |
| 7 | |
| 8 | * **Simple but functional** → |
| 9 | Fossil chat is designed to provide a convenient real-time |
| 10 | communication mechanism for geographically dispersed developers. |
| @@ -62,12 +61,12 @@ | |
| 61 | skin includes a "Chat" entry on the menu bar on wide screens for |
| 62 | people with chat privilege. There is also a "Chat" option on |
| 63 | the [Sitemap page](/sitemap), which means that chat will appear |
| 64 | as an option under the hamburger menu for many [skins](./customskin.md). |
| 65 | |
| 66 | Chat messages are subject to [Fossil's |
| 67 | full range of Markdown processing](/md_rules). Because chat messages are |
| 68 | stored as-is when they arrive from a client, this change applies |
| 69 | retroactively to messages stored by previous fossil versions. |
| 70 | |
| 71 | Files may be sent via chat using the file selection element at the |
| 72 | bottom of the page. If the desktop environment system supports it, |
| @@ -110,12 +109,12 @@ | |
| 109 | |
| 110 | ### <a id='connection'></a> Who's Online? |
| 111 | |
| 112 | Because the chat app has to be able to work over transient CGI-based |
| 113 | connections, as opposed to a stable socket connection to the server, |
| 114 | real-time tracking of "who's online" is not feasible. |
| 115 | Chat offers an optional feature, toggleable in the settings, |
| 116 | which can list users who have posted messages in the client's current |
| 117 | list of loaded messages. This is not the same thing as tracking who's |
| 118 | online, but it gives an overview of which users have been active most |
| 119 | recently, noting that "lurkers" (people who post no messages) will not |
| 120 | show up in that list, nor does the chat infrastructure have a way to |
| 121 |
+2
-3
| --- www/ckout-workflows.md | ||
| +++ www/ckout-workflows.md | ||
| @@ -88,12 +88,11 @@ | ||
| 88 | 88 | workflow above with `fossil up` commands. |
| 89 | 89 | |
| 90 | 90 | |
| 91 | 91 | #### <a id="open"></a> Opening a Repository by URI |
| 92 | 92 | |
| 93 | -In Fossil 2.12, we added a feature to simplify the single-worktree use | |
| 94 | -case: | |
| 93 | +You can instead open the repo’s URI directly: | |
| 95 | 94 | |
| 96 | 95 | mkdir work-dir |
| 97 | 96 | cd work-dir |
| 98 | 97 | fossil open https://example.com/repo |
| 99 | 98 | |
| @@ -109,11 +108,11 @@ | ||
| 109 | 108 | details.) |
| 110 | 109 | |
| 111 | 110 | |
| 112 | 111 | #### <a id="clone"></a> Git-Like Clone-and-Open |
| 113 | 112 | |
| 114 | -In Fossil 2.14, we added a more Git-like alternative: | |
| 113 | +Fossil also supports a more Git-like alternative: | |
| 115 | 114 | |
| 116 | 115 | fossil clone https://fossil-scm.org/fossil |
| 117 | 116 | cd fossil |
| 118 | 117 | |
| 119 | 118 | This results in a `fossil.fossil` repo DB file and a `fossil/` working |
| 120 | 119 |
| --- www/ckout-workflows.md | |
| +++ www/ckout-workflows.md | |
| @@ -88,12 +88,11 @@ | |
| 88 | workflow above with `fossil up` commands. |
| 89 | |
| 90 | |
| 91 | #### <a id="open"></a> Opening a Repository by URI |
| 92 | |
| 93 | In Fossil 2.12, we added a feature to simplify the single-worktree use |
| 94 | case: |
| 95 | |
| 96 | mkdir work-dir |
| 97 | cd work-dir |
| 98 | fossil open https://example.com/repo |
| 99 | |
| @@ -109,11 +108,11 @@ | |
| 109 | details.) |
| 110 | |
| 111 | |
| 112 | #### <a id="clone"></a> Git-Like Clone-and-Open |
| 113 | |
| 114 | In Fossil 2.14, we added a more Git-like alternative: |
| 115 | |
| 116 | fossil clone https://fossil-scm.org/fossil |
| 117 | cd fossil |
| 118 | |
| 119 | This results in a `fossil.fossil` repo DB file and a `fossil/` working |
| 120 |
| --- www/ckout-workflows.md | |
| +++ www/ckout-workflows.md | |
| @@ -88,12 +88,11 @@ | |
| 88 | workflow above with `fossil up` commands. |
| 89 | |
| 90 | |
| 91 | #### <a id="open"></a> Opening a Repository by URI |
| 92 | |
| 93 | You can instead open the repo’s URI directly: |
| 94 | |
| 95 | mkdir work-dir |
| 96 | cd work-dir |
| 97 | fossil open https://example.com/repo |
| 98 | |
| @@ -109,11 +108,11 @@ | |
| 108 | details.) |
| 109 | |
| 110 | |
| 111 | #### <a id="clone"></a> Git-Like Clone-and-Open |
| 112 | |
| 113 | Fossil also supports a more Git-like alternative: |
| 114 | |
| 115 | fossil clone https://fossil-scm.org/fossil |
| 116 | cd fossil |
| 117 | |
| 118 | This results in a `fossil.fossil` repo DB file and a `fossil/` working |
| 119 |
+10
-12
| --- www/customskin.md | ||
| +++ www/customskin.md | ||
| @@ -145,12 +145,12 @@ | ||
| 145 | 145 | </body> |
| 146 | 146 | </html> |
| 147 | 147 | |
| 148 | 148 | ## <a id="mainmenu"></a>Changing the Main Menu Contents |
| 149 | 149 | |
| 150 | -As of Fossil 2.15, the actual text content of the skin’s main menu is no | |
| 151 | -longer part of the skin proper if you’re using one of the stock skins. | |
| 150 | +The actual text content of the skin’s main menu is not | |
| 151 | +part of the skin proper if you’re using one of the stock skins. | |
| 152 | 152 | If you look at the Header section of the skin, you’ll find a |
| 153 | 153 | `<div class="mainmenu">` element whose contents are set by a short |
| 154 | 154 | [TH1](./th1.md) script from the contents of the **Main Menu** section of |
| 155 | 155 | the Setup → Configuration screen. |
| 156 | 156 | |
| @@ -220,11 +220,11 @@ | ||
| 220 | 220 | right is a boolean - "1" to activate the feature and "0" to |
| 221 | 221 | disable it. The "white-foreground:" setting should be set to |
| 222 | 222 | "1" if the page color has light-color text on a darker background, |
| 223 | 223 | and "0" if the page has dark text on a light-colored background. |
| 224 | 224 | |
| 225 | -If the "pikchr-foreground" setting (added in Fossil 2.14) | |
| 225 | +If the "pikchr-foreground" setting | |
| 226 | 226 | is defined and is not an empty string then it specifies a |
| 227 | 227 | foreground color to use for [pikchr diagrams](./pikchr.md). The |
| 228 | 228 | default pikchr foreground color is black, or white if the |
| 229 | 229 | "white-foreground" boolean is set. The "pikchr-background" |
| 230 | 230 | settings does the same for the pikchr diagram background color. |
| @@ -267,20 +267,18 @@ | ||
| 267 | 267 | |
| 268 | 268 | <pre> |
| 269 | 269 | <th1>builtin_request_js hbmenu.js</th1> |
| 270 | 270 | </pre> |
| 271 | 271 | |
| 272 | -The difference between styleScript and builtin_request_js | |
| 273 | -is that the styleScript command interprets the file | |
| 272 | +The difference between `styleScript` and `builtin_request_js` | |
| 273 | +is that the `styleScript` command interprets the file | |
| 274 | 274 | using TH1 and injects the content directly into the output |
| 275 | -stream, whereas the builtin_request_js command inserts the | |
| 276 | -javascript verbatim and does so at some unspecified future time | |
| 277 | -down inside the Fossil-generated footer. The built-in skins | |
| 278 | -of Fossil originally used the styleScript command to load | |
| 279 | -the hamburger menu javascript, but as of version 2.15 switched | |
| 280 | -to using the builtin_request_js method. You can use either | |
| 281 | -approach in custom skins that you right yourself. | |
| 275 | +stream, whereas the `builtin_request_js` command inserts the | |
| 276 | +Javascript verbatim and does so at some unspecified future time | |
| 277 | +down inside the Fossil-generated footer. | |
| 278 | +You can use either | |
| 279 | +approach in custom skins that you create. | |
| 282 | 280 | |
| 283 | 281 | Note that the "js.txt" file is *not* automatically inserted into |
| 284 | 282 | the generate HTML for a page. You, the skin designer, must |
| 285 | 283 | cause the javascript to be inserted by issuing appropriate |
| 286 | 284 | TH1 commands in the "header.txt" or "footer.txt" files.</dd> |
| 287 | 285 |
| --- www/customskin.md | |
| +++ www/customskin.md | |
| @@ -145,12 +145,12 @@ | |
| 145 | </body> |
| 146 | </html> |
| 147 | |
| 148 | ## <a id="mainmenu"></a>Changing the Main Menu Contents |
| 149 | |
| 150 | As of Fossil 2.15, the actual text content of the skin’s main menu is no |
| 151 | longer part of the skin proper if you’re using one of the stock skins. |
| 152 | If you look at the Header section of the skin, you’ll find a |
| 153 | `<div class="mainmenu">` element whose contents are set by a short |
| 154 | [TH1](./th1.md) script from the contents of the **Main Menu** section of |
| 155 | the Setup → Configuration screen. |
| 156 | |
| @@ -220,11 +220,11 @@ | |
| 220 | right is a boolean - "1" to activate the feature and "0" to |
| 221 | disable it. The "white-foreground:" setting should be set to |
| 222 | "1" if the page color has light-color text on a darker background, |
| 223 | and "0" if the page has dark text on a light-colored background. |
| 224 | |
| 225 | If the "pikchr-foreground" setting (added in Fossil 2.14) |
| 226 | is defined and is not an empty string then it specifies a |
| 227 | foreground color to use for [pikchr diagrams](./pikchr.md). The |
| 228 | default pikchr foreground color is black, or white if the |
| 229 | "white-foreground" boolean is set. The "pikchr-background" |
| 230 | settings does the same for the pikchr diagram background color. |
| @@ -267,20 +267,18 @@ | |
| 267 | |
| 268 | <pre> |
| 269 | <th1>builtin_request_js hbmenu.js</th1> |
| 270 | </pre> |
| 271 | |
| 272 | The difference between styleScript and builtin_request_js |
| 273 | is that the styleScript command interprets the file |
| 274 | using TH1 and injects the content directly into the output |
| 275 | stream, whereas the builtin_request_js command inserts the |
| 276 | javascript verbatim and does so at some unspecified future time |
| 277 | down inside the Fossil-generated footer. The built-in skins |
| 278 | of Fossil originally used the styleScript command to load |
| 279 | the hamburger menu javascript, but as of version 2.15 switched |
| 280 | to using the builtin_request_js method. You can use either |
| 281 | approach in custom skins that you right yourself. |
| 282 | |
| 283 | Note that the "js.txt" file is *not* automatically inserted into |
| 284 | the generate HTML for a page. You, the skin designer, must |
| 285 | cause the javascript to be inserted by issuing appropriate |
| 286 | TH1 commands in the "header.txt" or "footer.txt" files.</dd> |
| 287 |
| --- www/customskin.md | |
| +++ www/customskin.md | |
| @@ -145,12 +145,12 @@ | |
| 145 | </body> |
| 146 | </html> |
| 147 | |
| 148 | ## <a id="mainmenu"></a>Changing the Main Menu Contents |
| 149 | |
| 150 | The actual text content of the skin’s main menu is not |
| 151 | part of the skin proper if you’re using one of the stock skins. |
| 152 | If you look at the Header section of the skin, you’ll find a |
| 153 | `<div class="mainmenu">` element whose contents are set by a short |
| 154 | [TH1](./th1.md) script from the contents of the **Main Menu** section of |
| 155 | the Setup → Configuration screen. |
| 156 | |
| @@ -220,11 +220,11 @@ | |
| 220 | right is a boolean - "1" to activate the feature and "0" to |
| 221 | disable it. The "white-foreground:" setting should be set to |
| 222 | "1" if the page color has light-color text on a darker background, |
| 223 | and "0" if the page has dark text on a light-colored background. |
| 224 | |
| 225 | If the "pikchr-foreground" setting |
| 226 | is defined and is not an empty string then it specifies a |
| 227 | foreground color to use for [pikchr diagrams](./pikchr.md). The |
| 228 | default pikchr foreground color is black, or white if the |
| 229 | "white-foreground" boolean is set. The "pikchr-background" |
| 230 | settings does the same for the pikchr diagram background color. |
| @@ -267,20 +267,18 @@ | |
| 267 | |
| 268 | <pre> |
| 269 | <th1>builtin_request_js hbmenu.js</th1> |
| 270 | </pre> |
| 271 | |
| 272 | The difference between `styleScript` and `builtin_request_js` |
| 273 | is that the `styleScript` command interprets the file |
| 274 | using TH1 and injects the content directly into the output |
| 275 | stream, whereas the `builtin_request_js` command inserts the |
| 276 | Javascript verbatim and does so at some unspecified future time |
| 277 | down inside the Fossil-generated footer. |
| 278 | You can use either |
| 279 | approach in custom skins that you create. |
| 280 | |
| 281 | Note that the "js.txt" file is *not* automatically inserted into |
| 282 | the generate HTML for a page. You, the skin designer, must |
| 283 | cause the javascript to be inserted by issuing appropriate |
| 284 | TH1 commands in the "header.txt" or "footer.txt" files.</dd> |
| 285 |
+4
-3
| --- www/defcsp.md | ||
| +++ www/defcsp.md | ||
| @@ -77,13 +77,14 @@ | ||
| 77 | 77 | [svr]: ./server/ |
| 78 | 78 | |
| 79 | 79 | |
| 80 | 80 | ### <a id="img"></a> img-src * data: |
| 81 | 81 | |
| 82 | -As of Fossil 2.15, we don’t restrict the source of inline images at all. | |
| 83 | -You can pull them in from remote systems as well as pull them from | |
| 84 | -within the Fossil repository itself, or use `data:` URIs. | |
| 82 | +It was not always thus, but after careful consideration, we’ve chosen to | |
| 83 | +leave the source of inline images unrestricted by default in Fossil. | |
| 84 | +This allows you to pull them in from remote systems, to pull them from | |
| 85 | +within the Fossil repository itself, or to use `data:` URIs. | |
| 85 | 86 | |
| 86 | 87 | If you are certain all images come from only within the repository, you |
| 87 | 88 | can close off certain risks — tracking pixels, broken image format |
| 88 | 89 | decoders, system dialog box spoofing, etc. — by changing this to |
| 89 | 90 | “`img-src 'self'`” possibly followed by “`data:`” if you will also use |
| 90 | 91 |
| --- www/defcsp.md | |
| +++ www/defcsp.md | |
| @@ -77,13 +77,14 @@ | |
| 77 | [svr]: ./server/ |
| 78 | |
| 79 | |
| 80 | ### <a id="img"></a> img-src * data: |
| 81 | |
| 82 | As of Fossil 2.15, we don’t restrict the source of inline images at all. |
| 83 | You can pull them in from remote systems as well as pull them from |
| 84 | within the Fossil repository itself, or use `data:` URIs. |
| 85 | |
| 86 | If you are certain all images come from only within the repository, you |
| 87 | can close off certain risks — tracking pixels, broken image format |
| 88 | decoders, system dialog box spoofing, etc. — by changing this to |
| 89 | “`img-src 'self'`” possibly followed by “`data:`” if you will also use |
| 90 |
| --- www/defcsp.md | |
| +++ www/defcsp.md | |
| @@ -77,13 +77,14 @@ | |
| 77 | [svr]: ./server/ |
| 78 | |
| 79 | |
| 80 | ### <a id="img"></a> img-src * data: |
| 81 | |
| 82 | It was not always thus, but after careful consideration, we’ve chosen to |
| 83 | leave the source of inline images unrestricted by default in Fossil. |
| 84 | This allows you to pull them in from remote systems, to pull them from |
| 85 | within the Fossil repository itself, or to use `data:` URIs. |
| 86 | |
| 87 | If you are certain all images come from only within the repository, you |
| 88 | can close off certain risks — tracking pixels, broken image format |
| 89 | decoders, system dialog box spoofing, etc. — by changing this to |
| 90 | “`img-src 'self'`” possibly followed by “`data:`” if you will also use |
| 91 |
-3
| --- www/fileedit-page.md | ||
| +++ www/fileedit-page.md | ||
| @@ -262,13 +262,10 @@ | ||
| 262 | 262 | |
| 263 | 263 | ``` |
| 264 | 264 | myCustomWidget.on('eventName', ()=>fossil.page.notifyOfChange()); |
| 265 | 265 | ``` |
| 266 | 266 | |
| 267 | -(This feature requires fossil version 2.13 or later. In 2.12 it is | |
| 268 | -possible to do this but requires making use of a "leaky abstraction".) | |
| 269 | - | |
| 270 | 267 | Lastly, if the 3rd-party editor does *not* hide or remove the native |
| 271 | 268 | editor widget, and does not inject itself into the DOM on the caller's |
| 272 | 269 | behalf, we can replace the native widget with the 3rd-party one with: |
| 273 | 270 | |
| 274 | 271 | ```javascript |
| 275 | 272 |
| --- www/fileedit-page.md | |
| +++ www/fileedit-page.md | |
| @@ -262,13 +262,10 @@ | |
| 262 | |
| 263 | ``` |
| 264 | myCustomWidget.on('eventName', ()=>fossil.page.notifyOfChange()); |
| 265 | ``` |
| 266 | |
| 267 | (This feature requires fossil version 2.13 or later. In 2.12 it is |
| 268 | possible to do this but requires making use of a "leaky abstraction".) |
| 269 | |
| 270 | Lastly, if the 3rd-party editor does *not* hide or remove the native |
| 271 | editor widget, and does not inject itself into the DOM on the caller's |
| 272 | behalf, we can replace the native widget with the 3rd-party one with: |
| 273 | |
| 274 | ```javascript |
| 275 |
| --- www/fileedit-page.md | |
| +++ www/fileedit-page.md | |
| @@ -262,13 +262,10 @@ | |
| 262 | |
| 263 | ``` |
| 264 | myCustomWidget.on('eventName', ()=>fossil.page.notifyOfChange()); |
| 265 | ``` |
| 266 | |
| 267 | Lastly, if the 3rd-party editor does *not* hide or remove the native |
| 268 | editor widget, and does not inject itself into the DOM on the caller's |
| 269 | behalf, we can replace the native widget with the 3rd-party one with: |
| 270 | |
| 271 | ```javascript |
| 272 |
+4
-4
| --- www/fossil-v-git.wiki | ||
| +++ www/fossil-v-git.wiki | ||
| @@ -845,12 +845,12 @@ | ||
| 845 | 845 | [./hashpolicy.wiki|full backwards compatibility] to old SHA-1 based |
| 846 | 846 | repositories. |
| 847 | 847 | |
| 848 | 848 | In October 2019, after the last of the major binary |
| 849 | 849 | package repos offering Fossil upgraded to Fossil 2.<i>x</i>, |
| 850 | -we switched the default hash mode so that from | |
| 851 | -Fossil 2.10 forward, the conversion to SHA-3 is fully automatic. | |
| 850 | +we switched the default hash mode so that | |
| 851 | +the conversion to SHA-3 is fully automatic. | |
| 852 | 852 | This not |
| 853 | 853 | only solves the SHAttered problem, it should prevent a reoccurrence of |
| 854 | 854 | similar problems for the foreseeable future. |
| 855 | 855 | |
| 856 | 856 | Meanwhile, the Git community took until August 2018 to publish |
| @@ -951,12 +951,12 @@ | ||
| 951 | 951 | files] — unified diff formatted output — for accepting drive-by contributions, but it's a |
| 952 | 952 | lossy contribution path for both systems. Unlike Git PRs and Fossil |
| 953 | 953 | bundles, patch files collapse multiple checkins together, they don't |
| 954 | 954 | include check-in comments, and they cannot encode changes made above |
| 955 | 955 | the individual file content layer: you lose branching decisions, |
| 956 | - tag changes, file renames, and more when using patch files. Fossil | |
| 957 | - 2.16 adds [./patchcmd.md | a <tt>fossil patch</tt> command] that | |
| 956 | + tag changes, file renames, and more when using patch files. The | |
| 957 | + [./patchcmd.md | <tt>fossil patch</tt> command] | |
| 958 | 958 | also solves these problems, but it is because it works like a Fossil |
| 959 | 959 | bundle, only for uncommitted changes; it doesn't use Larry Wall's |
| 960 | 960 | <tt>patch</tt> tool to apply unified diff output to the receiving |
| 961 | 961 | Fossil checkout.</p></li> |
| 962 | 962 | </ol></i></small> |
| 963 | 963 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -845,12 +845,12 @@ | |
| 845 | [./hashpolicy.wiki|full backwards compatibility] to old SHA-1 based |
| 846 | repositories. |
| 847 | |
| 848 | In October 2019, after the last of the major binary |
| 849 | package repos offering Fossil upgraded to Fossil 2.<i>x</i>, |
| 850 | we switched the default hash mode so that from |
| 851 | Fossil 2.10 forward, the conversion to SHA-3 is fully automatic. |
| 852 | This not |
| 853 | only solves the SHAttered problem, it should prevent a reoccurrence of |
| 854 | similar problems for the foreseeable future. |
| 855 | |
| 856 | Meanwhile, the Git community took until August 2018 to publish |
| @@ -951,12 +951,12 @@ | |
| 951 | files] — unified diff formatted output — for accepting drive-by contributions, but it's a |
| 952 | lossy contribution path for both systems. Unlike Git PRs and Fossil |
| 953 | bundles, patch files collapse multiple checkins together, they don't |
| 954 | include check-in comments, and they cannot encode changes made above |
| 955 | the individual file content layer: you lose branching decisions, |
| 956 | tag changes, file renames, and more when using patch files. Fossil |
| 957 | 2.16 adds [./patchcmd.md | a <tt>fossil patch</tt> command] that |
| 958 | also solves these problems, but it is because it works like a Fossil |
| 959 | bundle, only for uncommitted changes; it doesn't use Larry Wall's |
| 960 | <tt>patch</tt> tool to apply unified diff output to the receiving |
| 961 | Fossil checkout.</p></li> |
| 962 | </ol></i></small> |
| 963 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -845,12 +845,12 @@ | |
| 845 | [./hashpolicy.wiki|full backwards compatibility] to old SHA-1 based |
| 846 | repositories. |
| 847 | |
| 848 | In October 2019, after the last of the major binary |
| 849 | package repos offering Fossil upgraded to Fossil 2.<i>x</i>, |
| 850 | we switched the default hash mode so that |
| 851 | the conversion to SHA-3 is fully automatic. |
| 852 | This not |
| 853 | only solves the SHAttered problem, it should prevent a reoccurrence of |
| 854 | similar problems for the foreseeable future. |
| 855 | |
| 856 | Meanwhile, the Git community took until August 2018 to publish |
| @@ -951,12 +951,12 @@ | |
| 951 | files] — unified diff formatted output — for accepting drive-by contributions, but it's a |
| 952 | lossy contribution path for both systems. Unlike Git PRs and Fossil |
| 953 | bundles, patch files collapse multiple checkins together, they don't |
| 954 | include check-in comments, and they cannot encode changes made above |
| 955 | the individual file content layer: you lose branching decisions, |
| 956 | tag changes, file renames, and more when using patch files. The |
| 957 | [./patchcmd.md | <tt>fossil patch</tt> command] |
| 958 | also solves these problems, but it is because it works like a Fossil |
| 959 | bundle, only for uncommitted changes; it doesn't use Larry Wall's |
| 960 | <tt>patch</tt> tool to apply unified diff output to the receiving |
| 961 | Fossil checkout.</p></li> |
| 962 | </ol></i></small> |
| 963 |
+3
-3
| --- www/gitusers.md | ||
| +++ www/gitusers.md | ||
| @@ -781,11 +781,11 @@ | ||
| 781 | 781 | |
| 782 | 782 | Because the `fossil git export` command has to work with both stock Git |
| 783 | 783 | and with GitHub, Fossil uses Git’s traditional default rather than |
| 784 | 784 | GitHub’s new default: your Fossil repo’s “trunk” branch becomes “master” |
| 785 | 785 | when [mirroring to GitHub][mirgh] unless you give the `--mainbranch` |
| 786 | -option added in Fossil 2.14. | |
| 786 | +option. | |
| 787 | 787 | |
| 788 | 788 | We do not know what happens on subsequent exports if you later rename |
| 789 | 789 | this branch on the GitHub side. |
| 790 | 790 | |
| 791 | 791 | [mbgh]: https://github.com/github/renaming |
| @@ -853,11 +853,11 @@ | ||
| 853 | 853 | [below](#dstat). |
| 854 | 854 | |
| 855 | 855 | * Use the Fossil web UI to diff existing commits. |
| 856 | 856 | |
| 857 | 857 | * To diff the current working directory contents against some parent |
| 858 | - instead, Fossil 2.17 expanded the diff command so it can produce | |
| 858 | + instead, Fossil’s diff command can produce | |
| 859 | 859 | colorized HTML output and open it in the OS’s default web browser. |
| 860 | 860 | For example, `fossil diff -by` will show side-by-side diffs. |
| 861 | 861 | |
| 862 | 862 | * Use the older `fossil diff --tk` option to do much the same using |
| 863 | 863 | Tcl/Tk instead of a browser. |
| @@ -1258,11 +1258,11 @@ | ||
| 1258 | 1258 | |
| 1259 | 1259 | fossil clone https://dev-server.example.com/repo |
| 1260 | 1260 | cd repo |
| 1261 | 1261 | fossil remote add work https://dev-server.example.com/repo |
| 1262 | 1262 | |
| 1263 | -We’ve chosen the new “`fossil clone URI`” syntax added in Fossil 2.14 rather than separate | |
| 1263 | +We’ve chosen the new “`fossil clone URI`” syntax rather than separate | |
| 1264 | 1264 | `clone` and `open` commands to make the parallel with Git clearer. [See |
| 1265 | 1265 | above](#mwd) for more on that topic. |
| 1266 | 1266 | |
| 1267 | 1267 | Our [`remote` command][rem] is longer than the Git equivalent because |
| 1268 | 1268 | Fossil currently has no short command |
| 1269 | 1269 |
| --- www/gitusers.md | |
| +++ www/gitusers.md | |
| @@ -781,11 +781,11 @@ | |
| 781 | |
| 782 | Because the `fossil git export` command has to work with both stock Git |
| 783 | and with GitHub, Fossil uses Git’s traditional default rather than |
| 784 | GitHub’s new default: your Fossil repo’s “trunk” branch becomes “master” |
| 785 | when [mirroring to GitHub][mirgh] unless you give the `--mainbranch` |
| 786 | option added in Fossil 2.14. |
| 787 | |
| 788 | We do not know what happens on subsequent exports if you later rename |
| 789 | this branch on the GitHub side. |
| 790 | |
| 791 | [mbgh]: https://github.com/github/renaming |
| @@ -853,11 +853,11 @@ | |
| 853 | [below](#dstat). |
| 854 | |
| 855 | * Use the Fossil web UI to diff existing commits. |
| 856 | |
| 857 | * To diff the current working directory contents against some parent |
| 858 | instead, Fossil 2.17 expanded the diff command so it can produce |
| 859 | colorized HTML output and open it in the OS’s default web browser. |
| 860 | For example, `fossil diff -by` will show side-by-side diffs. |
| 861 | |
| 862 | * Use the older `fossil diff --tk` option to do much the same using |
| 863 | Tcl/Tk instead of a browser. |
| @@ -1258,11 +1258,11 @@ | |
| 1258 | |
| 1259 | fossil clone https://dev-server.example.com/repo |
| 1260 | cd repo |
| 1261 | fossil remote add work https://dev-server.example.com/repo |
| 1262 | |
| 1263 | We’ve chosen the new “`fossil clone URI`” syntax added in Fossil 2.14 rather than separate |
| 1264 | `clone` and `open` commands to make the parallel with Git clearer. [See |
| 1265 | above](#mwd) for more on that topic. |
| 1266 | |
| 1267 | Our [`remote` command][rem] is longer than the Git equivalent because |
| 1268 | Fossil currently has no short command |
| 1269 |
| --- www/gitusers.md | |
| +++ www/gitusers.md | |
| @@ -781,11 +781,11 @@ | |
| 781 | |
| 782 | Because the `fossil git export` command has to work with both stock Git |
| 783 | and with GitHub, Fossil uses Git’s traditional default rather than |
| 784 | GitHub’s new default: your Fossil repo’s “trunk” branch becomes “master” |
| 785 | when [mirroring to GitHub][mirgh] unless you give the `--mainbranch` |
| 786 | option. |
| 787 | |
| 788 | We do not know what happens on subsequent exports if you later rename |
| 789 | this branch on the GitHub side. |
| 790 | |
| 791 | [mbgh]: https://github.com/github/renaming |
| @@ -853,11 +853,11 @@ | |
| 853 | [below](#dstat). |
| 854 | |
| 855 | * Use the Fossil web UI to diff existing commits. |
| 856 | |
| 857 | * To diff the current working directory contents against some parent |
| 858 | instead, Fossil’s diff command can produce |
| 859 | colorized HTML output and open it in the OS’s default web browser. |
| 860 | For example, `fossil diff -by` will show side-by-side diffs. |
| 861 | |
| 862 | * Use the older `fossil diff --tk` option to do much the same using |
| 863 | Tcl/Tk instead of a browser. |
| @@ -1258,11 +1258,11 @@ | |
| 1258 | |
| 1259 | fossil clone https://dev-server.example.com/repo |
| 1260 | cd repo |
| 1261 | fossil remote add work https://dev-server.example.com/repo |
| 1262 | |
| 1263 | We’ve chosen the new “`fossil clone URI`” syntax rather than separate |
| 1264 | `clone` and `open` commands to make the parallel with Git clearer. [See |
| 1265 | above](#mwd) for more on that topic. |
| 1266 | |
| 1267 | Our [`remote` command][rem] is longer than the Git equivalent because |
| 1268 | Fossil currently has no short command |
| 1269 |
+3
-3
| --- www/glossary.md | ||
| +++ www/glossary.md | ||
| @@ -432,13 +432,13 @@ | ||
| 432 | 432 | * Your repository’s Home page is a good candidate for the wiki, as is |
| 433 | 433 | documentation meant for use only with the current version of the |
| 434 | 434 | repository’s contents. |
| 435 | 435 | |
| 436 | 436 | * If you are at all uncertain whether to use the wiki or the embedded |
| 437 | - documentation feature, prefer the latter, since it is more powerful | |
| 438 | - and, with the addition of the [`/fileedit` feature][fef] in Fossil | |
| 439 | - 2.12, it’s nearly as easy to use. | |
| 437 | + documentation feature, prefer the latter, since it is inherently | |
| 438 | + more powerful, and when you use the [`/fileedit` feature][fef], the | |
| 439 | + workflow is scarcely different from using the wiki. | |
| 440 | 440 | |
| 441 | 441 | (This very file is embedded documentation: clone |
| 442 | 442 | [Fossil’s self-hosting repository][fshr] and you will find it as |
| 443 | 443 | `www/glossary.md`.) |
| 444 | 444 | |
| 445 | 445 |
| --- www/glossary.md | |
| +++ www/glossary.md | |
| @@ -432,13 +432,13 @@ | |
| 432 | * Your repository’s Home page is a good candidate for the wiki, as is |
| 433 | documentation meant for use only with the current version of the |
| 434 | repository’s contents. |
| 435 | |
| 436 | * If you are at all uncertain whether to use the wiki or the embedded |
| 437 | documentation feature, prefer the latter, since it is more powerful |
| 438 | and, with the addition of the [`/fileedit` feature][fef] in Fossil |
| 439 | 2.12, it’s nearly as easy to use. |
| 440 | |
| 441 | (This very file is embedded documentation: clone |
| 442 | [Fossil’s self-hosting repository][fshr] and you will find it as |
| 443 | `www/glossary.md`.) |
| 444 | |
| 445 |
| --- www/glossary.md | |
| +++ www/glossary.md | |
| @@ -432,13 +432,13 @@ | |
| 432 | * Your repository’s Home page is a good candidate for the wiki, as is |
| 433 | documentation meant for use only with the current version of the |
| 434 | repository’s contents. |
| 435 | |
| 436 | * If you are at all uncertain whether to use the wiki or the embedded |
| 437 | documentation feature, prefer the latter, since it is inherently |
| 438 | more powerful, and when you use the [`/fileedit` feature][fef], the |
| 439 | workflow is scarcely different from using the wiki. |
| 440 | |
| 441 | (This very file is embedded documentation: clone |
| 442 | [Fossil’s self-hosting repository][fshr] and you will find it as |
| 443 | `www/glossary.md`.) |
| 444 | |
| 445 |
+11
-11
| --- www/javascript.md | ||
| +++ www/javascript.md | ||
| @@ -321,11 +321,11 @@ | ||
| 321 | 321 | [wt]: https://fossil-scm.org/home/timeline |
| 322 | 322 | |
| 323 | 323 | |
| 324 | 324 | ### <a id="wedit"></a>The New Wiki Editor |
| 325 | 325 | |
| 326 | -The [new wiki editor][fwt] added in Fossil 2.12 has many new features, a | |
| 326 | +The [new wiki editor][fwt] has many new features, a | |
| 327 | 327 | few of which are impossible to get without use of JavaScript. |
| 328 | 328 | |
| 329 | 329 | First, it allows in-browser previews without losing client-side editor |
| 330 | 330 | state, such as where your cursor is. With the old editor, you had to |
| 331 | 331 | re-locate the place you were last editing on each preview, which would |
| @@ -355,13 +355,13 @@ | ||
| 355 | 355 | JavaScript in order to react to editor button clicks like the “**B**” |
| 356 | 356 | button, meaning “make \[selected\] text boldface.” There is no standard |
| 357 | 357 | WYSIWYG editor component in browsers, doubtless because it’s relatively |
| 358 | 358 | straightforward to create one using JavaScript. |
| 359 | 359 | |
| 360 | -_Graceful Fallback:_ Unlike in the Fossil 2.11 and earlier days, there | |
| 361 | -is no longer a script-free wiki editor mode. This is not from lack of | |
| 362 | -desire, only because the person who wrote the new wiki editor didn’t | |
| 360 | +_Graceful Fallback:_ Fossil’s lack of | |
| 361 | +a script-free wiki editor mode is not from lack of | |
| 362 | +desire, but because the person who wrote the new wiki editor didn’t | |
| 363 | 363 | want to maintain three different editors. (New Ajaxy editor, old |
| 364 | 364 | script-free HTML form based editor, and the old WYSIWYG JavaScript-based |
| 365 | 365 | editor.) If someone wants to implement a `<noscript>` alternative to the |
| 366 | 366 | new wiki editor, we will likely accept that [contribution][cg] as long |
| 367 | 367 | as it doesn’t interfere with the new editor. (The same goes for adding |
| @@ -396,11 +396,11 @@ | ||
| 396 | 396 | [fwt]: ./wikitheory.wiki |
| 397 | 397 | |
| 398 | 398 | |
| 399 | 399 | ### <a id="fedit"></a>The File Editor |
| 400 | 400 | |
| 401 | -Fossil 2.12 adds the [optional file editor feature][fedit], which works | |
| 401 | +Fossil’s [optional file editor feature][fedit] works | |
| 402 | 402 | much like [the new wiki editor](#wedit), only on files committed to the |
| 403 | 403 | repository. |
| 404 | 404 | |
| 405 | 405 | The original designed purpose for this feature is to allow [embedded |
| 406 | 406 | documentation][edoc] to be interactively edited in the same way that |
| @@ -437,14 +437,14 @@ | ||
| 437 | 437 | _Potential Better Workaround:_ Someone sufficiently interested could |
| 438 | 438 | [provide a patch][cg] to add a `<noscript>` wrapped HTML button that |
| 439 | 439 | would reload the page with this parameter included/excluded to implement |
| 440 | 440 | the toggle via a server round-trip. |
| 441 | 441 | |
| 442 | -As of Fossil 2.12, there is also a JavaScript-based interactive method | |
| 442 | +A related feature is Fossil’s JavaScript-based interactive method | |
| 443 | 443 | for selecting a range of lines by clicking the line numbers when they’re |
| 444 | -visible, then copying the resulting URL to share your selection with | |
| 445 | -others. | |
| 444 | +visible. JavaScript lets us copy the resulting URL to the clipboard | |
| 445 | +to share your selection with others. | |
| 446 | 446 | |
| 447 | 447 | _Workaround:_ These interactive features would be difficult and |
| 448 | 448 | expensive (in terms of network I/O) to implement without JavaScript. A |
| 449 | 449 | far simpler alternative is to manually edit the URL, per above. |
| 450 | 450 | |
| @@ -465,11 +465,11 @@ | ||
| 465 | 465 | |
| 466 | 466 | _Graceful Fallback:_ Manually scroll both boxes to sync their views. |
| 467 | 467 | |
| 468 | 468 | ### <a id="diffcontext"></a>Diff Context Loading |
| 469 | 469 | |
| 470 | -As of version 2.17, fossil adds the ability for the diff views to | |
| 470 | +Fossil’s diff views can | |
| 471 | 471 | dynamically load more lines of context around changed blocks. The UI |
| 472 | 472 | controls for this feature are injected using JavaScript when the page |
| 473 | 473 | initializes and make use of XHR requests to fetch data from the |
| 474 | 474 | fossil instance. |
| 475 | 475 | |
| @@ -566,11 +566,11 @@ | ||
| 566 | 566 | core developers to do this work for them. |
| 567 | 567 | |
| 568 | 568 | |
| 569 | 569 | ### <a id="chat"></a>Chat |
| 570 | 570 | |
| 571 | -The [chat feature](./chat.md) added in Fossil 2.14 is deeply dependent | |
| 571 | +The [chat feature](./chat.md) is deeply dependent | |
| 572 | 572 | on JavaScript. There is no obvious way to do this sort of thing without |
| 573 | 573 | active client-side code of some sort. |
| 574 | 574 | |
| 575 | 575 | _Potential Workaround:_ It would not be especially difficult for someone |
| 576 | 576 | sufficiently motivated to build a Fossil chat gateway, connecting to |
| @@ -584,11 +584,11 @@ | ||
| 584 | 584 | gateway bidirectional should be possible as well, as long as it properly |
| 585 | 585 | uses SQLite transactions. |
| 586 | 586 | |
| 587 | 587 | ### <a id="brlist"></a>List of branches |
| 588 | 588 | |
| 589 | -Since Fossil 2.16 the [`/brlist`](/brlist) page uses JavaScript to enable | |
| 589 | +The [`/brlist`](/brlist) page uses JavaScript to enable | |
| 590 | 590 | selection of several branches for further study via `/timeline`. |
| 591 | 591 | Client-side script interactively responds to checkboxes' events |
| 592 | 592 | and constructs a special hyperlink in the submenu. |
| 593 | 593 | Clicking this hyperlink loads a `/timeline` page that shows |
| 594 | 594 | only these selected branches (and the related check-ins). |
| 595 | 595 |
| --- www/javascript.md | |
| +++ www/javascript.md | |
| @@ -321,11 +321,11 @@ | |
| 321 | [wt]: https://fossil-scm.org/home/timeline |
| 322 | |
| 323 | |
| 324 | ### <a id="wedit"></a>The New Wiki Editor |
| 325 | |
| 326 | The [new wiki editor][fwt] added in Fossil 2.12 has many new features, a |
| 327 | few of which are impossible to get without use of JavaScript. |
| 328 | |
| 329 | First, it allows in-browser previews without losing client-side editor |
| 330 | state, such as where your cursor is. With the old editor, you had to |
| 331 | re-locate the place you were last editing on each preview, which would |
| @@ -355,13 +355,13 @@ | |
| 355 | JavaScript in order to react to editor button clicks like the “**B**” |
| 356 | button, meaning “make \[selected\] text boldface.” There is no standard |
| 357 | WYSIWYG editor component in browsers, doubtless because it’s relatively |
| 358 | straightforward to create one using JavaScript. |
| 359 | |
| 360 | _Graceful Fallback:_ Unlike in the Fossil 2.11 and earlier days, there |
| 361 | is no longer a script-free wiki editor mode. This is not from lack of |
| 362 | desire, only because the person who wrote the new wiki editor didn’t |
| 363 | want to maintain three different editors. (New Ajaxy editor, old |
| 364 | script-free HTML form based editor, and the old WYSIWYG JavaScript-based |
| 365 | editor.) If someone wants to implement a `<noscript>` alternative to the |
| 366 | new wiki editor, we will likely accept that [contribution][cg] as long |
| 367 | as it doesn’t interfere with the new editor. (The same goes for adding |
| @@ -396,11 +396,11 @@ | |
| 396 | [fwt]: ./wikitheory.wiki |
| 397 | |
| 398 | |
| 399 | ### <a id="fedit"></a>The File Editor |
| 400 | |
| 401 | Fossil 2.12 adds the [optional file editor feature][fedit], which works |
| 402 | much like [the new wiki editor](#wedit), only on files committed to the |
| 403 | repository. |
| 404 | |
| 405 | The original designed purpose for this feature is to allow [embedded |
| 406 | documentation][edoc] to be interactively edited in the same way that |
| @@ -437,14 +437,14 @@ | |
| 437 | _Potential Better Workaround:_ Someone sufficiently interested could |
| 438 | [provide a patch][cg] to add a `<noscript>` wrapped HTML button that |
| 439 | would reload the page with this parameter included/excluded to implement |
| 440 | the toggle via a server round-trip. |
| 441 | |
| 442 | As of Fossil 2.12, there is also a JavaScript-based interactive method |
| 443 | for selecting a range of lines by clicking the line numbers when they’re |
| 444 | visible, then copying the resulting URL to share your selection with |
| 445 | others. |
| 446 | |
| 447 | _Workaround:_ These interactive features would be difficult and |
| 448 | expensive (in terms of network I/O) to implement without JavaScript. A |
| 449 | far simpler alternative is to manually edit the URL, per above. |
| 450 | |
| @@ -465,11 +465,11 @@ | |
| 465 | |
| 466 | _Graceful Fallback:_ Manually scroll both boxes to sync their views. |
| 467 | |
| 468 | ### <a id="diffcontext"></a>Diff Context Loading |
| 469 | |
| 470 | As of version 2.17, fossil adds the ability for the diff views to |
| 471 | dynamically load more lines of context around changed blocks. The UI |
| 472 | controls for this feature are injected using JavaScript when the page |
| 473 | initializes and make use of XHR requests to fetch data from the |
| 474 | fossil instance. |
| 475 | |
| @@ -566,11 +566,11 @@ | |
| 566 | core developers to do this work for them. |
| 567 | |
| 568 | |
| 569 | ### <a id="chat"></a>Chat |
| 570 | |
| 571 | The [chat feature](./chat.md) added in Fossil 2.14 is deeply dependent |
| 572 | on JavaScript. There is no obvious way to do this sort of thing without |
| 573 | active client-side code of some sort. |
| 574 | |
| 575 | _Potential Workaround:_ It would not be especially difficult for someone |
| 576 | sufficiently motivated to build a Fossil chat gateway, connecting to |
| @@ -584,11 +584,11 @@ | |
| 584 | gateway bidirectional should be possible as well, as long as it properly |
| 585 | uses SQLite transactions. |
| 586 | |
| 587 | ### <a id="brlist"></a>List of branches |
| 588 | |
| 589 | Since Fossil 2.16 the [`/brlist`](/brlist) page uses JavaScript to enable |
| 590 | selection of several branches for further study via `/timeline`. |
| 591 | Client-side script interactively responds to checkboxes' events |
| 592 | and constructs a special hyperlink in the submenu. |
| 593 | Clicking this hyperlink loads a `/timeline` page that shows |
| 594 | only these selected branches (and the related check-ins). |
| 595 |
| --- www/javascript.md | |
| +++ www/javascript.md | |
| @@ -321,11 +321,11 @@ | |
| 321 | [wt]: https://fossil-scm.org/home/timeline |
| 322 | |
| 323 | |
| 324 | ### <a id="wedit"></a>The New Wiki Editor |
| 325 | |
| 326 | The [new wiki editor][fwt] has many new features, a |
| 327 | few of which are impossible to get without use of JavaScript. |
| 328 | |
| 329 | First, it allows in-browser previews without losing client-side editor |
| 330 | state, such as where your cursor is. With the old editor, you had to |
| 331 | re-locate the place you were last editing on each preview, which would |
| @@ -355,13 +355,13 @@ | |
| 355 | JavaScript in order to react to editor button clicks like the “**B**” |
| 356 | button, meaning “make \[selected\] text boldface.” There is no standard |
| 357 | WYSIWYG editor component in browsers, doubtless because it’s relatively |
| 358 | straightforward to create one using JavaScript. |
| 359 | |
| 360 | _Graceful Fallback:_ Fossil’s lack of |
| 361 | a script-free wiki editor mode is not from lack of |
| 362 | desire, but because the person who wrote the new wiki editor didn’t |
| 363 | want to maintain three different editors. (New Ajaxy editor, old |
| 364 | script-free HTML form based editor, and the old WYSIWYG JavaScript-based |
| 365 | editor.) If someone wants to implement a `<noscript>` alternative to the |
| 366 | new wiki editor, we will likely accept that [contribution][cg] as long |
| 367 | as it doesn’t interfere with the new editor. (The same goes for adding |
| @@ -396,11 +396,11 @@ | |
| 396 | [fwt]: ./wikitheory.wiki |
| 397 | |
| 398 | |
| 399 | ### <a id="fedit"></a>The File Editor |
| 400 | |
| 401 | Fossil’s [optional file editor feature][fedit] works |
| 402 | much like [the new wiki editor](#wedit), only on files committed to the |
| 403 | repository. |
| 404 | |
| 405 | The original designed purpose for this feature is to allow [embedded |
| 406 | documentation][edoc] to be interactively edited in the same way that |
| @@ -437,14 +437,14 @@ | |
| 437 | _Potential Better Workaround:_ Someone sufficiently interested could |
| 438 | [provide a patch][cg] to add a `<noscript>` wrapped HTML button that |
| 439 | would reload the page with this parameter included/excluded to implement |
| 440 | the toggle via a server round-trip. |
| 441 | |
| 442 | A related feature is Fossil’s JavaScript-based interactive method |
| 443 | for selecting a range of lines by clicking the line numbers when they’re |
| 444 | visible. JavaScript lets us copy the resulting URL to the clipboard |
| 445 | to share your selection with others. |
| 446 | |
| 447 | _Workaround:_ These interactive features would be difficult and |
| 448 | expensive (in terms of network I/O) to implement without JavaScript. A |
| 449 | far simpler alternative is to manually edit the URL, per above. |
| 450 | |
| @@ -465,11 +465,11 @@ | |
| 465 | |
| 466 | _Graceful Fallback:_ Manually scroll both boxes to sync their views. |
| 467 | |
| 468 | ### <a id="diffcontext"></a>Diff Context Loading |
| 469 | |
| 470 | Fossil’s diff views can |
| 471 | dynamically load more lines of context around changed blocks. The UI |
| 472 | controls for this feature are injected using JavaScript when the page |
| 473 | initializes and make use of XHR requests to fetch data from the |
| 474 | fossil instance. |
| 475 | |
| @@ -566,11 +566,11 @@ | |
| 566 | core developers to do this work for them. |
| 567 | |
| 568 | |
| 569 | ### <a id="chat"></a>Chat |
| 570 | |
| 571 | The [chat feature](./chat.md) is deeply dependent |
| 572 | on JavaScript. There is no obvious way to do this sort of thing without |
| 573 | active client-side code of some sort. |
| 574 | |
| 575 | _Potential Workaround:_ It would not be especially difficult for someone |
| 576 | sufficiently motivated to build a Fossil chat gateway, connecting to |
| @@ -584,11 +584,11 @@ | |
| 584 | gateway bidirectional should be possible as well, as long as it properly |
| 585 | uses SQLite transactions. |
| 586 | |
| 587 | ### <a id="brlist"></a>List of branches |
| 588 | |
| 589 | The [`/brlist`](/brlist) page uses JavaScript to enable |
| 590 | selection of several branches for further study via `/timeline`. |
| 591 | Client-side script interactively responds to checkboxes' events |
| 592 | and constructs a special hyperlink in the submenu. |
| 593 | Clicking this hyperlink loads a `/timeline` page that shows |
| 594 | only these selected branches (and the related check-ins). |
| 595 |
+1
-2
| --- www/mirrortogithub.md | ||
| +++ www/mirrortogithub.md | ||
| @@ -100,12 +100,11 @@ | ||
| 100 | 100 | Git. Be careful not to mess with the `.mirror_state` directory or |
| 101 | 101 | any of its contents. Do not put those files under Git management. Do |
| 102 | 102 | not edit or delete them. |
| 103 | 103 | |
| 104 | 104 | * The name of the "trunk" branch is automatically translated into "master" |
| 105 | - in the Git mirror unless you give the `--mainbranch` option, | |
| 106 | - added in Fossil 2.14. | |
| 105 | + in the Git mirror unless you give the `--mainbranch` option. | |
| 107 | 106 | |
| 108 | 107 | * Only check-ins and simple tags are translated to Git. Git does not |
| 109 | 108 | support wiki or tickets or unversioned content or any of the other |
| 110 | 109 | features of Fossil that make it so convenient to use, so those other |
| 111 | 110 | elements cannot be mirrored in Git. |
| 112 | 111 |
| --- www/mirrortogithub.md | |
| +++ www/mirrortogithub.md | |
| @@ -100,12 +100,11 @@ | |
| 100 | Git. Be careful not to mess with the `.mirror_state` directory or |
| 101 | any of its contents. Do not put those files under Git management. Do |
| 102 | not edit or delete them. |
| 103 | |
| 104 | * The name of the "trunk" branch is automatically translated into "master" |
| 105 | in the Git mirror unless you give the `--mainbranch` option, |
| 106 | added in Fossil 2.14. |
| 107 | |
| 108 | * Only check-ins and simple tags are translated to Git. Git does not |
| 109 | support wiki or tickets or unversioned content or any of the other |
| 110 | features of Fossil that make it so convenient to use, so those other |
| 111 | elements cannot be mirrored in Git. |
| 112 |
| --- www/mirrortogithub.md | |
| +++ www/mirrortogithub.md | |
| @@ -100,12 +100,11 @@ | |
| 100 | Git. Be careful not to mess with the `.mirror_state` directory or |
| 101 | any of its contents. Do not put those files under Git management. Do |
| 102 | not edit or delete them. |
| 103 | |
| 104 | * The name of the "trunk" branch is automatically translated into "master" |
| 105 | in the Git mirror unless you give the `--mainbranch` option. |
| 106 | |
| 107 | * Only check-ins and simple tags are translated to Git. Git does not |
| 108 | support wiki or tickets or unversioned content or any of the other |
| 109 | features of Fossil that make it so convenient to use, so those other |
| 110 | elements cannot be mirrored in Git. |
| 111 |
+1
-4
| --- www/server/debian/nginx.md | ||
| +++ www/server/debian/nginx.md | ||
| @@ -297,14 +297,11 @@ | ||
| 297 | 297 | `/etc/fail2ban/filter.d/nginx-fossil-login.conf`: |
| 298 | 298 | |
| 299 | 299 | [Definition] |
| 300 | 300 | failregex = ^<HOST> - .*POST .*/login HTTP/..." 401 |
| 301 | 301 | |
| 302 | -That teaches `fail2ban` how to recognize the errors logged by Fossil | |
| 303 | -[as of 2.14](/info/39d7eb0e22). (Earlier versions of Fossil returned | |
| 304 | -HTTP status code 200 for this, so you couldn’t distinguish a successful | |
| 305 | -login from a failure.) | |
| 302 | +That teaches `fail2ban` how to recognize the errors logged by Fossil. | |
| 306 | 303 | |
| 307 | 304 | Then in `/etc/fail2ban/jail.local`, add this section: |
| 308 | 305 | |
| 309 | 306 | [nginx-fossil-login] |
| 310 | 307 | enabled = true |
| 311 | 308 |
| --- www/server/debian/nginx.md | |
| +++ www/server/debian/nginx.md | |
| @@ -297,14 +297,11 @@ | |
| 297 | `/etc/fail2ban/filter.d/nginx-fossil-login.conf`: |
| 298 | |
| 299 | [Definition] |
| 300 | failregex = ^<HOST> - .*POST .*/login HTTP/..." 401 |
| 301 | |
| 302 | That teaches `fail2ban` how to recognize the errors logged by Fossil |
| 303 | [as of 2.14](/info/39d7eb0e22). (Earlier versions of Fossil returned |
| 304 | HTTP status code 200 for this, so you couldn’t distinguish a successful |
| 305 | login from a failure.) |
| 306 | |
| 307 | Then in `/etc/fail2ban/jail.local`, add this section: |
| 308 | |
| 309 | [nginx-fossil-login] |
| 310 | enabled = true |
| 311 |
| --- www/server/debian/nginx.md | |
| +++ www/server/debian/nginx.md | |
| @@ -297,14 +297,11 @@ | |
| 297 | `/etc/fail2ban/filter.d/nginx-fossil-login.conf`: |
| 298 | |
| 299 | [Definition] |
| 300 | failregex = ^<HOST> - .*POST .*/login HTTP/..." 401 |
| 301 | |
| 302 | That teaches `fail2ban` how to recognize the errors logged by Fossil. |
| 303 | |
| 304 | Then in `/etc/fail2ban/jail.local`, add this section: |
| 305 | |
| 306 | [nginx-fossil-login] |
| 307 | enabled = true |
| 308 |
+2
-2
| --- www/server/windows/service.md | ||
| +++ www/server/windows/service.md | ||
| @@ -9,12 +9,12 @@ | ||
| 9 | 9 | 2. You have PowerShell 5.1 or above installed. |
| 10 | 10 | |
| 11 | 11 | ## Place Fossil on Server |
| 12 | 12 | |
| 13 | 13 | However you obtained your copy of Fossil, it is recommended that you follow |
| 14 | -Windows conventions and place it within `\Program Files\FossilSCM`. Since | |
| 15 | -Fossil 2.10 is a 64bit binary, this is the proper location for the executable. | |
| 14 | +Windows conventions and place it within `\Program Files\FossilSCM`, the | |
| 15 | +proper location for the official 64-bit binary. | |
| 16 | 16 | This way Fossil is at an expected location and you will have minimal issues with |
| 17 | 17 | Windows interfering in your ability to run Fossil as a service. You will need |
| 18 | 18 | Administrative rights to place fossil at the recommended location. If you will |
| 19 | 19 | only be running Fossil as a service, you do not need to add this location to the |
| 20 | 20 | path, though you may do so if you wish. |
| 21 | 21 |
| --- www/server/windows/service.md | |
| +++ www/server/windows/service.md | |
| @@ -9,12 +9,12 @@ | |
| 9 | 2. You have PowerShell 5.1 or above installed. |
| 10 | |
| 11 | ## Place Fossil on Server |
| 12 | |
| 13 | However you obtained your copy of Fossil, it is recommended that you follow |
| 14 | Windows conventions and place it within `\Program Files\FossilSCM`. Since |
| 15 | Fossil 2.10 is a 64bit binary, this is the proper location for the executable. |
| 16 | This way Fossil is at an expected location and you will have minimal issues with |
| 17 | Windows interfering in your ability to run Fossil as a service. You will need |
| 18 | Administrative rights to place fossil at the recommended location. If you will |
| 19 | only be running Fossil as a service, you do not need to add this location to the |
| 20 | path, though you may do so if you wish. |
| 21 |
| --- www/server/windows/service.md | |
| +++ www/server/windows/service.md | |
| @@ -9,12 +9,12 @@ | |
| 9 | 2. You have PowerShell 5.1 or above installed. |
| 10 | |
| 11 | ## Place Fossil on Server |
| 12 | |
| 13 | However you obtained your copy of Fossil, it is recommended that you follow |
| 14 | Windows conventions and place it within `\Program Files\FossilSCM`, the |
| 15 | proper location for the official 64-bit binary. |
| 16 | This way Fossil is at an expected location and you will have minimal issues with |
| 17 | Windows interfering in your ability to run Fossil as a service. You will need |
| 18 | Administrative rights to place fossil at the recommended location. If you will |
| 19 | only be running Fossil as a service, you do not need to add this location to the |
| 20 | path, though you may do so if you wish. |
| 21 |
| --- www/server/windows/stunnel.md | ||
| +++ www/server/windows/stunnel.md | ||
| @@ -11,16 +11,10 @@ | ||
| 11 | 11 | |
| 12 | 12 | 1. You have Administrative access to a Windows 2012r2 or above server. |
| 13 | 13 | 2. You have PowerShell 5.1 or above installed. |
| 14 | 14 | 3. You have acquired a certificate either from a Public CA or an Internal CA. |
| 15 | 15 | |
| 16 | -These instructions were tested with Fossil 2.10 and stunnel 5.55. Other | |
| 17 | -versions may not function in a similar manner. There is a bug in Fossil 2.9 and | |
| 18 | -earlier that prevents these versions of Fossil from properly constructing https | |
| 19 | -URLs when used with stunnel as a proxy. Please make sure you are using Fossil | |
| 20 | -2.10 or later on Windows. | |
| 21 | - | |
| 22 | 16 | ## Configure Fossil Service for https |
| 23 | 17 | |
| 24 | 18 | Due to the need for the `--https` option for successfully using Fossil with |
| 25 | 19 | stunnel, we will use [Advanced service installation using PowerShell](./service.md#PowerShell). |
| 26 | 20 | We will need to change the command to install the Fossil Service to configure |
| 27 | 21 |
| --- www/server/windows/stunnel.md | |
| +++ www/server/windows/stunnel.md | |
| @@ -11,16 +11,10 @@ | |
| 11 | |
| 12 | 1. You have Administrative access to a Windows 2012r2 or above server. |
| 13 | 2. You have PowerShell 5.1 or above installed. |
| 14 | 3. You have acquired a certificate either from a Public CA or an Internal CA. |
| 15 | |
| 16 | These instructions were tested with Fossil 2.10 and stunnel 5.55. Other |
| 17 | versions may not function in a similar manner. There is a bug in Fossil 2.9 and |
| 18 | earlier that prevents these versions of Fossil from properly constructing https |
| 19 | URLs when used with stunnel as a proxy. Please make sure you are using Fossil |
| 20 | 2.10 or later on Windows. |
| 21 | |
| 22 | ## Configure Fossil Service for https |
| 23 | |
| 24 | Due to the need for the `--https` option for successfully using Fossil with |
| 25 | stunnel, we will use [Advanced service installation using PowerShell](./service.md#PowerShell). |
| 26 | We will need to change the command to install the Fossil Service to configure |
| 27 |
| --- www/server/windows/stunnel.md | |
| +++ www/server/windows/stunnel.md | |
| @@ -11,16 +11,10 @@ | |
| 11 | |
| 12 | 1. You have Administrative access to a Windows 2012r2 or above server. |
| 13 | 2. You have PowerShell 5.1 or above installed. |
| 14 | 3. You have acquired a certificate either from a Public CA or an Internal CA. |
| 15 | |
| 16 | ## Configure Fossil Service for https |
| 17 | |
| 18 | Due to the need for the `--https` option for successfully using Fossil with |
| 19 | stunnel, we will use [Advanced service installation using PowerShell](./service.md#PowerShell). |
| 20 | We will need to change the command to install the Fossil Service to configure |
| 21 |
+3
-4
| --- www/ssl.wiki | ||
| +++ www/ssl.wiki | ||
| @@ -121,11 +121,11 @@ | ||
| 121 | 121 | "always" if you want Fossil to remember your decision. |
| 122 | 122 | |
| 123 | 123 | If you are cloning from or syncing to Fossil servers that use a |
| 124 | 124 | certificate signed by a well-known CA or one of its delegates, Fossil |
| 125 | 125 | still has to know which CA roots to trust. When this fails, you get an |
| 126 | -error message that looks like this in Fossil 2.11 and newer: | |
| 126 | +error message that looks like this: | |
| 127 | 127 | |
| 128 | 128 | <pre> |
| 129 | 129 | Unable to verify SSL cert from fossil-scm.org |
| 130 | 130 | subject: CN = sqlite.org |
| 131 | 131 | issuer: C = US, O = Let's Encrypt, CN = Let's Encrypt Authority X3 |
| @@ -226,13 +226,12 @@ | ||
| 226 | 226 | which explains what to do to authenticate with the server. |
| 227 | 227 | |
| 228 | 228 | |
| 229 | 229 | <h2 id="server">Server-Side Configuration</h2> |
| 230 | 230 | |
| 231 | -Fossil's built-in HTTP server got [./ssl-server.md | TLS support] in | |
| 232 | -December 2021, released as version 2.18 in early 2022. Prior to that, | |
| 233 | -system administrators that wanted to add TLS support to a Fossil server | |
| 231 | +Before Fossil's built-in HTTP server gained [./ssl-server.md | TLS support], | |
| 232 | +system administrators that wanted to add this | |
| 234 | 233 | had to put it behind a reverse proxy that would do the translation. |
| 235 | 234 | Since advantages remain for delegating TLS to another layer in the |
| 236 | 235 | stack, instructions for doing so continue to be included in our |
| 237 | 236 | documentation, such as: |
| 238 | 237 | |
| 239 | 238 |
| --- www/ssl.wiki | |
| +++ www/ssl.wiki | |
| @@ -121,11 +121,11 @@ | |
| 121 | "always" if you want Fossil to remember your decision. |
| 122 | |
| 123 | If you are cloning from or syncing to Fossil servers that use a |
| 124 | certificate signed by a well-known CA or one of its delegates, Fossil |
| 125 | still has to know which CA roots to trust. When this fails, you get an |
| 126 | error message that looks like this in Fossil 2.11 and newer: |
| 127 | |
| 128 | <pre> |
| 129 | Unable to verify SSL cert from fossil-scm.org |
| 130 | subject: CN = sqlite.org |
| 131 | issuer: C = US, O = Let's Encrypt, CN = Let's Encrypt Authority X3 |
| @@ -226,13 +226,12 @@ | |
| 226 | which explains what to do to authenticate with the server. |
| 227 | |
| 228 | |
| 229 | <h2 id="server">Server-Side Configuration</h2> |
| 230 | |
| 231 | Fossil's built-in HTTP server got [./ssl-server.md | TLS support] in |
| 232 | December 2021, released as version 2.18 in early 2022. Prior to that, |
| 233 | system administrators that wanted to add TLS support to a Fossil server |
| 234 | had to put it behind a reverse proxy that would do the translation. |
| 235 | Since advantages remain for delegating TLS to another layer in the |
| 236 | stack, instructions for doing so continue to be included in our |
| 237 | documentation, such as: |
| 238 | |
| 239 |
| --- www/ssl.wiki | |
| +++ www/ssl.wiki | |
| @@ -121,11 +121,11 @@ | |
| 121 | "always" if you want Fossil to remember your decision. |
| 122 | |
| 123 | If you are cloning from or syncing to Fossil servers that use a |
| 124 | certificate signed by a well-known CA or one of its delegates, Fossil |
| 125 | still has to know which CA roots to trust. When this fails, you get an |
| 126 | error message that looks like this: |
| 127 | |
| 128 | <pre> |
| 129 | Unable to verify SSL cert from fossil-scm.org |
| 130 | subject: CN = sqlite.org |
| 131 | issuer: C = US, O = Let's Encrypt, CN = Let's Encrypt Authority X3 |
| @@ -226,13 +226,12 @@ | |
| 226 | which explains what to do to authenticate with the server. |
| 227 | |
| 228 | |
| 229 | <h2 id="server">Server-Side Configuration</h2> |
| 230 | |
| 231 | Before Fossil's built-in HTTP server gained [./ssl-server.md | TLS support], |
| 232 | system administrators that wanted to add this |
| 233 | had to put it behind a reverse proxy that would do the translation. |
| 234 | Since advantages remain for delegating TLS to another layer in the |
| 235 | stack, instructions for doing so continue to be included in our |
| 236 | documentation, such as: |
| 237 | |
| 238 |
-2
| --- www/th1.md | ||
| +++ www/th1.md | ||
| @@ -281,12 +281,10 @@ | ||
| 281 | 281 | |
| 282 | 282 | |
| 283 | 283 | <a id="capexpr"></a>TH1 capexpr Command |
| 284 | 284 | ----------------------------------------------------- |
| 285 | 285 | |
| 286 | -Added in Fossil 2.15. | |
| 287 | - | |
| 288 | 286 | * capexpr CAPABILITY-EXPR |
| 289 | 287 | |
| 290 | 288 | The capability expression is a list. Each term of the list is a |
| 291 | 289 | cluster of [capability letters](./caps/ref.html). |
| 292 | 290 | The overall expression is true if any |
| 293 | 291 |
| --- www/th1.md | |
| +++ www/th1.md | |
| @@ -281,12 +281,10 @@ | |
| 281 | |
| 282 | |
| 283 | <a id="capexpr"></a>TH1 capexpr Command |
| 284 | ----------------------------------------------------- |
| 285 | |
| 286 | Added in Fossil 2.15. |
| 287 | |
| 288 | * capexpr CAPABILITY-EXPR |
| 289 | |
| 290 | The capability expression is a list. Each term of the list is a |
| 291 | cluster of [capability letters](./caps/ref.html). |
| 292 | The overall expression is true if any |
| 293 |
| --- www/th1.md | |
| +++ www/th1.md | |
| @@ -281,12 +281,10 @@ | |
| 281 | |
| 282 | |
| 283 | <a id="capexpr"></a>TH1 capexpr Command |
| 284 | ----------------------------------------------------- |
| 285 | |
| 286 | * capexpr CAPABILITY-EXPR |
| 287 | |
| 288 | The capability expression is a list. Each term of the list is a |
| 289 | cluster of [capability letters](./caps/ref.html). |
| 290 | The overall expression is true if any |
| 291 |