Fossil SCM
Added a link to the backups doc from the "benefits of a server" doc, fixed a few more grammar problems, and fixed a few URLs in prior commits.
Commit
4f9c6210cd940cb417065ff0a81c68478158188850056644721308159f96213e
Parent
05e79793d85c082…
1 file changed
+9
-8
+9
-8
| --- www/server/whyuseaserver.wiki | ||
| +++ www/server/whyuseaserver.wiki | ||
| @@ -35,19 +35,20 @@ | ||
| 35 | 35 | in sync with each other without having to interrupt each other |
| 36 | 36 | constantly to set up a peer-to-peer sync. |
| 37 | 37 | |
| 38 | 38 | 3. <b>A server provides project leaders with up-to-date status.</b><p> |
| 39 | 39 | Project coordinators and BDFLs can click on a link or two at the |
| 40 | - central Fossil server for a project, and quickly tell what is | |
| 41 | - going on. They can do this from anywhere, even from their phones, | |
| 42 | - without needing to actually sync to the device they are using. | |
| 40 | + central Fossil server for a project and quickly tell what is | |
| 41 | + going on. They can do this from anywhere — even from their phones | |
| 42 | + — without needing to actually sync to the device they are using. | |
| 43 | 43 | |
| 44 | 44 | 4. <b>A server provides automatic off-site backups.</b><p> |
| 45 | 45 | A Fossil server is an automatic remote backup for all the work |
| 46 | - going into a project. You can even set up multiple servers, at | |
| 47 | - multiple sites, with automatic synchronization between them, for | |
| 48 | - added redundancy. Such a set up means that no work is lost due | |
| 46 | + going into a project. ([../backup.md | Within limits].) | |
| 47 | + You can even set up multiple servers at | |
| 48 | + multiple sites with automatic synchronization between them for | |
| 49 | + added redundancy. Such a setup means that no work is lost due | |
| 49 | 50 | to a single machine failure. |
| 50 | 51 | |
| 51 | 52 | 5. <b>A server consolidates [https://www.sqlite.org/howtocorrupt.html |
| 52 | 53 | | SQLite corruption risk mitigation] to a single point.</b><p> |
| 53 | 54 | The concerns in section 1 of that document assume you have direct |
| @@ -67,10 +68,10 @@ | ||
| 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 that risk database corruption.<p> |
| 71 | 72 | |
| 72 | - 6. <b>A server allows [./caps/ | Fossil's RBAC system] to work.</b><p> | |
| 73 | + 6. <b>A server allows [../caps/ | Fossil's RBAC system] to work.</b><p> | |
| 73 | 74 | The role-based access control (RBAC) system in Fossil only works |
| 74 | 75 | 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 | + ([../caps/#webonly | Details].) If you want its benefits, you need | |
| 76 | 77 | a Fossil server setup of some kind. |
| 77 | 78 |
| --- www/server/whyuseaserver.wiki | |
| +++ www/server/whyuseaserver.wiki | |
| @@ -35,19 +35,20 @@ | |
| 35 | in sync with each other without having to interrupt each other |
| 36 | constantly to set up a peer-to-peer sync. |
| 37 | |
| 38 | 3. <b>A server provides project leaders with up-to-date status.</b><p> |
| 39 | Project coordinators and BDFLs can click on a link or two at the |
| 40 | central Fossil server for a project, and quickly tell what is |
| 41 | going on. They can do this from anywhere, even from their phones, |
| 42 | without needing to actually sync to the device they are using. |
| 43 | |
| 44 | 4. <b>A server provides automatic off-site backups.</b><p> |
| 45 | A Fossil server is an automatic remote backup for all the work |
| 46 | going into a project. You can even set up multiple servers, at |
| 47 | multiple sites, with automatic synchronization between them, for |
| 48 | added redundancy. Such a set up means that no work is lost due |
| 49 | to a single machine failure. |
| 50 | |
| 51 | 5. <b>A server consolidates [https://www.sqlite.org/howtocorrupt.html |
| 52 | | SQLite corruption risk mitigation] to a single point.</b><p> |
| 53 | The concerns in section 1 of that document assume you have direct |
| @@ -67,10 +68,10 @@ | |
| 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 that 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 | |
| @@ -35,19 +35,20 @@ | |
| 35 | in sync with each other without having to interrupt each other |
| 36 | constantly to set up a peer-to-peer sync. |
| 37 | |
| 38 | 3. <b>A server provides project leaders with up-to-date status.</b><p> |
| 39 | Project coordinators and BDFLs can click on a link or two at the |
| 40 | central Fossil server for a project and quickly tell what is |
| 41 | going on. They can do this from anywhere — even from their phones |
| 42 | — without needing to actually sync to the device they are using. |
| 43 | |
| 44 | 4. <b>A server provides automatic off-site backups.</b><p> |
| 45 | A Fossil server is an automatic remote backup for all the work |
| 46 | going into a project. ([../backup.md | Within limits].) |
| 47 | You can even set up multiple servers at |
| 48 | multiple sites with automatic synchronization between them for |
| 49 | added redundancy. Such a setup means that no work is lost due |
| 50 | to a single machine failure. |
| 51 | |
| 52 | 5. <b>A server consolidates [https://www.sqlite.org/howtocorrupt.html |
| 53 | | SQLite corruption risk mitigation] to a single point.</b><p> |
| 54 | The concerns in section 1 of that document assume you have direct |
| @@ -67,10 +68,10 @@ | |
| 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 that risk database corruption.<p> |
| 72 | |
| 73 | 6. <b>A server allows [../caps/ | Fossil's RBAC system] to work.</b><p> |
| 74 | The role-based access control (RBAC) system in Fossil only works |
| 75 | when the remote system is on the other side of an HTTP barrier. |
| 76 | ([../caps/#webonly | Details].) If you want its benefits, you need |
| 77 | a Fossil server setup of some kind. |
| 78 |