Fossil SCM
Added a paragraph to point #5 in the "benefits of a server" doc to point to Larry Brasfield's new "SQLite Over a Network, Caveats and Considerations" article and to give a Fossil-specific gloss on it.
Commit
130abdcec218ad48058e8a747147dd3f84cde82c8eae20a74aed7c69f290f975
Parent
f17ab2989ac55a6…
1 file changed
+10
-1
+10
-1
| --- www/server/whyuseaserver.wiki | ||
| +++ www/server/whyuseaserver.wiki | ||
| @@ -3,11 +3,12 @@ | ||
| 3 | 3 | <h2>No Server Required</h2> |
| 4 | 4 | |
| 5 | 5 | Fossil does not require a central server. |
| 6 | 6 | Data sharing and synchronization can be entirely peer-to-peer. |
| 7 | 7 | Fossil uses |
| 8 | -[https://en.wikipedia.org/wiki/Conflict-free_replicated_data_type|conflict-free replicated data types] | |
| 8 | +[https://en.wikipedia.org/wiki/Conflict-free_replicated_data_type | | |
| 9 | +conflict-free replicated data types] | |
| 9 | 10 | to ensure that (in the limit) all participating peers see the same content. |
| 10 | 11 | |
| 11 | 12 | <h2>But, a Server Can Be Useful</h2> |
| 12 | 13 | |
| 13 | 14 | Fossil does not require a server, but a server can be very useful. |
| @@ -66,11 +67,19 @@ | ||
| 66 | 67 | #4 above.<p> |
| 67 | 68 | Sections 3.2 and the entirety of section 7 are no concern with |
| 68 | 69 | Fossil at all, since it's primarily written by the creator and |
| 69 | 70 | primary maintainer of SQLite, so you can be certain Fossil doesn't |
| 70 | 71 | actively pursue coding strategies known to risk database corruption.<p> |
| 72 | + <p>For another take on this topic, see the article | |
| 73 | + "[https://sqlite.org/useovernet.html | SQLite Over a Network, | |
| 74 | + Caveats and Considerations]". Fossil runs in rollback mode by | |
| 75 | + default per recommendation #3 at the end of that article, and a | |
| 76 | + Fossil server operates as a network proxy for the underlying | |
| 77 | + SQLite repository DB per recommendation #2. This <i>may</i> permit | |
| 78 | + you to safely switch it into WAL mode (<b>fossil rebuild --wal</b>) | |
| 79 | + depending on the underlying storage used by the server itself.</p> | |
| 71 | 80 | |
| 72 | 81 | 6. <b>A server allows [../caps/ | Fossil's RBAC system] to work.</b><p> |
| 73 | 82 | The role-based access control (RBAC) system in Fossil only works |
| 74 | 83 | when the remote system is on the other side of an HTTP barrier. |
| 75 | 84 | ([../caps/#webonly | Details].) If you want its benefits, you need |
| 76 | 85 | a Fossil server setup of some kind. |
| 77 | 86 |
| --- www/server/whyuseaserver.wiki | |
| +++ www/server/whyuseaserver.wiki | |
| @@ -3,11 +3,12 @@ | |
| 3 | <h2>No Server Required</h2> |
| 4 | |
| 5 | Fossil does not require a central server. |
| 6 | Data sharing and synchronization can be entirely peer-to-peer. |
| 7 | Fossil uses |
| 8 | [https://en.wikipedia.org/wiki/Conflict-free_replicated_data_type|conflict-free replicated data types] |
| 9 | to ensure that (in the limit) all participating peers see the same content. |
| 10 | |
| 11 | <h2>But, a Server Can Be Useful</h2> |
| 12 | |
| 13 | Fossil does not require a server, but a server can be very useful. |
| @@ -66,11 +67,19 @@ | |
| 66 | #4 above.<p> |
| 67 | Sections 3.2 and the entirety of section 7 are no concern with |
| 68 | Fossil at all, since it's primarily written by the creator and |
| 69 | primary maintainer of SQLite, so you can be certain Fossil doesn't |
| 70 | actively pursue coding strategies known to risk database corruption.<p> |
| 71 | |
| 72 | 6. <b>A server allows [../caps/ | Fossil's RBAC system] to work.</b><p> |
| 73 | The role-based access control (RBAC) system in Fossil only works |
| 74 | when the remote system is on the other side of an HTTP barrier. |
| 75 | ([../caps/#webonly | Details].) If you want its benefits, you need |
| 76 | a Fossil server setup of some kind. |
| 77 |
| --- www/server/whyuseaserver.wiki | |
| +++ www/server/whyuseaserver.wiki | |
| @@ -3,11 +3,12 @@ | |
| 3 | <h2>No Server Required</h2> |
| 4 | |
| 5 | Fossil does not require a central server. |
| 6 | Data sharing and synchronization can be entirely peer-to-peer. |
| 7 | Fossil uses |
| 8 | [https://en.wikipedia.org/wiki/Conflict-free_replicated_data_type | |
| 9 | conflict-free replicated data types] |
| 10 | to ensure that (in the limit) all participating peers see the same content. |
| 11 | |
| 12 | <h2>But, a Server Can Be Useful</h2> |
| 13 | |
| 14 | Fossil does not require a server, but a server can be very useful. |
| @@ -66,11 +67,19 @@ | |
| 67 | #4 above.<p> |
| 68 | Sections 3.2 and the entirety of section 7 are no concern with |
| 69 | Fossil at all, since it's primarily written by the creator and |
| 70 | primary maintainer of SQLite, so you can be certain Fossil doesn't |
| 71 | actively pursue coding strategies known to risk database corruption.<p> |
| 72 | <p>For another take on this topic, see the article |
| 73 | "[https://sqlite.org/useovernet.html | SQLite Over a Network, |
| 74 | Caveats and Considerations]". Fossil runs in rollback mode by |
| 75 | default per recommendation #3 at the end of that article, and a |
| 76 | Fossil server operates as a network proxy for the underlying |
| 77 | SQLite repository DB per recommendation #2. This <i>may</i> permit |
| 78 | you to safely switch it into WAL mode (<b>fossil rebuild --wal</b>) |
| 79 | depending on the underlying storage used by the server itself.</p> |
| 80 | |
| 81 | 6. <b>A server allows [../caps/ | Fossil's RBAC system] to work.</b><p> |
| 82 | The role-based access control (RBAC) system in Fossil only works |
| 83 | when the remote system is on the other side of an HTTP barrier. |
| 84 | ([../caps/#webonly | Details].) If you want its benefits, you need |
| 85 | a Fossil server setup of some kind. |
| 86 |