Fossil SCM
Drop "efficiency" claims in fossil-v-git, as the term is not quite right to describe the point. Use "self-sufficient" instead.
Commit
41b34915bb816ab61607142bbb1a94a1bd5fdd196c9d1c085dd1ff6cfe9db712
Parent
6369d7b31c9e79e…
1 file changed
+9
-10
+9
-10
| --- www/fossil-v-git.wiki | ||
| +++ www/fossil-v-git.wiki | ||
| @@ -43,13 +43,13 @@ | ||
| 43 | 43 | <td>VCS, tickets, wiki, docs, notes, forum, UI, |
| 44 | 44 | [https://en.wikipedia.org/wiki/Role-based_access_control|RBAC]</td> |
| 45 | 45 | <td><a href="#features">2.1 ↓</a></td> |
| 46 | 46 | </tr> |
| 47 | 47 | <tr> |
| 48 | - <td>Sprawling and inefficient</td> | |
| 49 | - <td>Self-contained and efficient</td> | |
| 50 | - <td><a href="#efficient">2.2 ↓</a></td> | |
| 48 | + <td>Sprawling collection of programs</td> | |
| 49 | + <td>Self-contained, stand-alone executable</td> | |
| 50 | + <td><a href="#selfcontained">2.2 ↓</a></td> | |
| 51 | 51 | </tr> |
| 52 | 52 | <tr> |
| 53 | 53 | <td>One-off custom pile-of-files data store</td> |
| 54 | 54 | <td>[https://sqlite.org/famous.html|The most popular database in the world]</td> |
| 55 | 55 | <td><a href="#durable">2.3 ↓</a></td> |
| @@ -154,11 +154,11 @@ | ||
| 154 | 154 | history, and so forth.² That means you get a copy of this very article |
| 155 | 155 | and all of its historical versions, plus the same for all of the other |
| 156 | 156 | public content on this site. |
| 157 | 157 | |
| 158 | 158 | |
| 159 | -<h3 id="efficient" name="effective">2.2 Efficient</h3> | |
| 159 | +<h3 id="selfcontained" name="selfcontained">2.2 Self Contained</h3> | |
| 160 | 160 | |
| 161 | 161 | Git is actually a collection of many small tools, each doing one small |
| 162 | 162 | part of the job, which can be recombined (by experts) to perform |
| 163 | 163 | powerful operations. Git has a lot of complexity and many dependencies, |
| 164 | 164 | so that most people end up installing it via some kind of package |
| @@ -220,16 +220,15 @@ | ||
| 220 | 220 | thing you could call a "server" these days, but when you go to host that |
| 221 | 221 | in the cloud, you can expect to pay about 8× as much to comfortably host |
| 222 | 222 | GitLab as for Fossil.³ This difference is largely due to basic |
| 223 | 223 | technology choices: Ruby and PostgreSQL vs C and SQLite. |
| 224 | 224 | |
| 225 | -The Fossil project itself is [./selfhost.wiki|hosted on a very small | |
| 226 | -VPS], and we've received many reports on the Fossil forum about people | |
| 227 | -successfully hosting Fossil service on bare-bones $5/month VPS hosts, | |
| 228 | -spare Raspberry Pi boards, and other small hosts. | |
| 229 | - | |
| 230 | - | |
| 225 | +The Fossil project itself is [./selfhost.wiki|hosted on a small and | |
| 226 | +inexpensive VPS]. A bare-bones $5/month VPS or a | |
| 227 | +spare Raspberry Pi is sufficient to run a full-up project | |
| 228 | +site, complete with tickets, wiki, and forum, in addition to | |
| 229 | +being a code repository. | |
| 231 | 230 | |
| 232 | 231 | <h3 id="durable" name="database">2.3 Durable</h3> |
| 233 | 232 | |
| 234 | 233 | The baseline data structures for Fossil and Git are the same, modulo |
| 235 | 234 | formatting details. Both systems manage a |
| 236 | 235 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -43,13 +43,13 @@ | |
| 43 | <td>VCS, tickets, wiki, docs, notes, forum, UI, |
| 44 | [https://en.wikipedia.org/wiki/Role-based_access_control|RBAC]</td> |
| 45 | <td><a href="#features">2.1 ↓</a></td> |
| 46 | </tr> |
| 47 | <tr> |
| 48 | <td>Sprawling and inefficient</td> |
| 49 | <td>Self-contained and efficient</td> |
| 50 | <td><a href="#efficient">2.2 ↓</a></td> |
| 51 | </tr> |
| 52 | <tr> |
| 53 | <td>One-off custom pile-of-files data store</td> |
| 54 | <td>[https://sqlite.org/famous.html|The most popular database in the world]</td> |
| 55 | <td><a href="#durable">2.3 ↓</a></td> |
| @@ -154,11 +154,11 @@ | |
| 154 | history, and so forth.² That means you get a copy of this very article |
| 155 | and all of its historical versions, plus the same for all of the other |
| 156 | public content on this site. |
| 157 | |
| 158 | |
| 159 | <h3 id="efficient" name="effective">2.2 Efficient</h3> |
| 160 | |
| 161 | Git is actually a collection of many small tools, each doing one small |
| 162 | part of the job, which can be recombined (by experts) to perform |
| 163 | powerful operations. Git has a lot of complexity and many dependencies, |
| 164 | so that most people end up installing it via some kind of package |
| @@ -220,16 +220,15 @@ | |
| 220 | thing you could call a "server" these days, but when you go to host that |
| 221 | in the cloud, you can expect to pay about 8× as much to comfortably host |
| 222 | GitLab as for Fossil.³ This difference is largely due to basic |
| 223 | technology choices: Ruby and PostgreSQL vs C and SQLite. |
| 224 | |
| 225 | The Fossil project itself is [./selfhost.wiki|hosted on a very small |
| 226 | VPS], and we've received many reports on the Fossil forum about people |
| 227 | successfully hosting Fossil service on bare-bones $5/month VPS hosts, |
| 228 | spare Raspberry Pi boards, and other small hosts. |
| 229 | |
| 230 | |
| 231 | |
| 232 | <h3 id="durable" name="database">2.3 Durable</h3> |
| 233 | |
| 234 | The baseline data structures for Fossil and Git are the same, modulo |
| 235 | formatting details. Both systems manage a |
| 236 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -43,13 +43,13 @@ | |
| 43 | <td>VCS, tickets, wiki, docs, notes, forum, UI, |
| 44 | [https://en.wikipedia.org/wiki/Role-based_access_control|RBAC]</td> |
| 45 | <td><a href="#features">2.1 ↓</a></td> |
| 46 | </tr> |
| 47 | <tr> |
| 48 | <td>Sprawling collection of programs</td> |
| 49 | <td>Self-contained, stand-alone executable</td> |
| 50 | <td><a href="#selfcontained">2.2 ↓</a></td> |
| 51 | </tr> |
| 52 | <tr> |
| 53 | <td>One-off custom pile-of-files data store</td> |
| 54 | <td>[https://sqlite.org/famous.html|The most popular database in the world]</td> |
| 55 | <td><a href="#durable">2.3 ↓</a></td> |
| @@ -154,11 +154,11 @@ | |
| 154 | history, and so forth.² That means you get a copy of this very article |
| 155 | and all of its historical versions, plus the same for all of the other |
| 156 | public content on this site. |
| 157 | |
| 158 | |
| 159 | <h3 id="selfcontained" name="selfcontained">2.2 Self Contained</h3> |
| 160 | |
| 161 | Git is actually a collection of many small tools, each doing one small |
| 162 | part of the job, which can be recombined (by experts) to perform |
| 163 | powerful operations. Git has a lot of complexity and many dependencies, |
| 164 | so that most people end up installing it via some kind of package |
| @@ -220,16 +220,15 @@ | |
| 220 | thing you could call a "server" these days, but when you go to host that |
| 221 | in the cloud, you can expect to pay about 8× as much to comfortably host |
| 222 | GitLab as for Fossil.³ This difference is largely due to basic |
| 223 | technology choices: Ruby and PostgreSQL vs C and SQLite. |
| 224 | |
| 225 | The Fossil project itself is [./selfhost.wiki|hosted on a small and |
| 226 | inexpensive VPS]. A bare-bones $5/month VPS or a |
| 227 | spare Raspberry Pi is sufficient to run a full-up project |
| 228 | site, complete with tickets, wiki, and forum, in addition to |
| 229 | being a code repository. |
| 230 | |
| 231 | <h3 id="durable" name="database">2.3 Durable</h3> |
| 232 | |
| 233 | The baseline data structures for Fossil and Git are the same, modulo |
| 234 | formatting details. Both systems manage a |
| 235 |