Fossil SCM
Added paragraph about hosting efficiency of Fossil vs Gitlab (to make it an apples-to-apples comparison) to the fossil-v-git doc.
Commit
f631c7c82e20ffcf4a7e1ef916d4d160886330d67a78ba4031f4e517acd1d5e9
Parent
47e495d26b2a122…
1 file changed
+18
+18
| --- www/fossil-v-git.wiki | ||
| +++ www/fossil-v-git.wiki | ||
| @@ -376,10 +376,28 @@ | ||
| 376 | 376 | The designer of Git says that the Unix philosophy is to have lots of |
| 377 | 377 | small tools that collaborate to get the job done. The designer of |
| 378 | 378 | Fossil says that the Unix philosophy is "It just works." Both |
| 379 | 379 | individuals have written their DVCSes to reflect their own view |
| 380 | 380 | of the "Unix philosophy." |
| 381 | + | |
| 382 | +This point combines with the [#features|feature set differences] in an | |
| 383 | +interesting way: although you can add third-party pieces to Git to give | |
| 384 | +it equivalent functionality to what Fossil delivers out of the box, the | |
| 385 | +resulting system will doubtlessly be far less efficient than an | |
| 386 | +equivalent Fossil setup. We've received many reports on the Fossil forum | |
| 387 | +about people successfully hosting Fossil service on bare-bones $5/month | |
| 388 | +VPS hosts, spare Raspberry Pi boards, and similarly resource-constrained | |
| 389 | +environments. Contrast a feature-requivalent like Gitlab, which has | |
| 390 | +[https://docs.gitlab.com/ee/install/requirements.html|far steeper | |
| 391 | +demands] due to basic differences in technology choices: Ruby and | |
| 392 | +PostgreSQL vs C and SQLite! Gitlab's recommended minimum requirements | |
| 393 | +are fine when you're dedicating a local rack server to Gitlab, since | |
| 394 | +that's about the smallest thing you could call a "server" these days, | |
| 395 | +but when you go to host that in the cloud, their 8 GiB of RAM and 2 | |
| 396 | +CPU core recommendation costs about 8⨉ as much as a comfortable hosting | |
| 397 | +environment for Fossil in a recent check at a major VPS hosting | |
| 398 | +provider. | |
| 381 | 399 | |
| 382 | 400 | |
| 383 | 401 | <h3 id="checkouts">2.6 One vs. Many Check-outs per Repository</h3> |
| 384 | 402 | |
| 385 | 403 | A "repository" in Git is a pile-of-files in the ".git" subdirectory |
| 386 | 404 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -376,10 +376,28 @@ | |
| 376 | The designer of Git says that the Unix philosophy is to have lots of |
| 377 | small tools that collaborate to get the job done. The designer of |
| 378 | Fossil says that the Unix philosophy is "It just works." Both |
| 379 | individuals have written their DVCSes to reflect their own view |
| 380 | of the "Unix philosophy." |
| 381 | |
| 382 | |
| 383 | <h3 id="checkouts">2.6 One vs. Many Check-outs per Repository</h3> |
| 384 | |
| 385 | A "repository" in Git is a pile-of-files in the ".git" subdirectory |
| 386 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -376,10 +376,28 @@ | |
| 376 | The designer of Git says that the Unix philosophy is to have lots of |
| 377 | small tools that collaborate to get the job done. The designer of |
| 378 | Fossil says that the Unix philosophy is "It just works." Both |
| 379 | individuals have written their DVCSes to reflect their own view |
| 380 | of the "Unix philosophy." |
| 381 | |
| 382 | This point combines with the [#features|feature set differences] in an |
| 383 | interesting way: although you can add third-party pieces to Git to give |
| 384 | it equivalent functionality to what Fossil delivers out of the box, the |
| 385 | resulting system will doubtlessly be far less efficient than an |
| 386 | equivalent Fossil setup. We've received many reports on the Fossil forum |
| 387 | about people successfully hosting Fossil service on bare-bones $5/month |
| 388 | VPS hosts, spare Raspberry Pi boards, and similarly resource-constrained |
| 389 | environments. Contrast a feature-requivalent like Gitlab, which has |
| 390 | [https://docs.gitlab.com/ee/install/requirements.html|far steeper |
| 391 | demands] due to basic differences in technology choices: Ruby and |
| 392 | PostgreSQL vs C and SQLite! Gitlab's recommended minimum requirements |
| 393 | are fine when you're dedicating a local rack server to Gitlab, since |
| 394 | that's about the smallest thing you could call a "server" these days, |
| 395 | but when you go to host that in the cloud, their 8 GiB of RAM and 2 |
| 396 | CPU core recommendation costs about 8⨉ as much as a comfortable hosting |
| 397 | environment for Fossil in a recent check at a major VPS hosting |
| 398 | provider. |
| 399 | |
| 400 | |
| 401 | <h3 id="checkouts">2.6 One vs. Many Check-outs per Repository</h3> |
| 402 | |
| 403 | A "repository" in Git is a pile-of-files in the ".git" subdirectory |
| 404 |