Fossil SCM
Added Digital Ocean pricing footnote to fossil-v-git.wiki to back up the GitLab comparison. Also clarified the "smallest thing you could call a server" comment.
Commit
efc873ec6845ea25ef498fd13da187ef59b9ea6ed6ed2a2c68e8f502d540accb
Parent
431245edce60233…
1 file changed
+11
-4
+11
-4
| --- www/fossil-v-git.wiki | ||
| +++ www/fossil-v-git.wiki | ||
| @@ -127,14 +127,15 @@ | ||
| 127 | 127 | [https://about.gitlab.com/|GitLab], a third-party extension to Git |
| 128 | 128 | wrapping it in many features, making it roughly Fossil-equivalent, |
| 129 | 129 | though [https://docs.gitlab.com/ee/install/requirements.html|much more |
| 130 | 130 | resource hungry] and hence more costly to run than the equivalent |
| 131 | 131 | Fossil setup. GitLab's basic requirements are easy to accept when you're dedicating |
| 132 | -a local rack server or blade to it, since that's about the smallest | |
| 132 | +a local rack server or blade to it, since its minimum requirements are | |
| 133 | +more or less a description of the smallest | |
| 133 | 134 | thing you could call a "server" these days, but when you go to host that |
| 134 | 135 | in the cloud, you can expect to pay about 8⨉ as much to comfortably host |
| 135 | -GitLab as for Fossil. This difference is largely due to basic | |
| 136 | +GitLab as for Fossil.³ This difference is largely due to basic | |
| 136 | 137 | technology choices: Ruby and PostgreSQL vs C and SQLite. |
| 137 | 138 | |
| 138 | 139 | The Fossil project itself is [./selfhost.wiki|hosted on a very small |
| 139 | 140 | VPS], and we've received many reports on the Fossil forum about people |
| 140 | 141 | successfully hosting Fossil service on bare-bones $5/month VPS hosts, |
| @@ -207,11 +208,11 @@ | ||
| 207 | 208 | facilities Fossil needs to do its thing. (Network sockets, file locking, |
| 208 | 209 | etc.) There are certainly well-known platforms Fossil hasn't been ported |
| 209 | 210 | to yet, but that's most likely due to lack of interest rather than |
| 210 | 211 | inherent difficulties in doing the port. We believe the most stringent |
| 211 | 212 | limit on its portability is that it assumes at least a 32-bit CPU and |
| 212 | -several megs of flat-addressed memory.³ Fossil isn't quite as | |
| 213 | +several megs of flat-addressed memory.⁴ Fossil isn't quite as | |
| 213 | 214 | [https://www.sqlite.org/custombuild.html|portable as SQLite], but it's |
| 214 | 215 | close. |
| 215 | 216 | |
| 216 | 217 | About half of the code in Fossil is actually an embedded copy of the |
| 217 | 218 | current version of SQLite. Much of what is Fossil-specific after you set |
| @@ -323,11 +324,11 @@ | ||
| 323 | 324 | [https://www.git-scm.com/docs/git-request-pull|pull requests] offer |
| 324 | 325 | a low-friction path to accepting |
| 325 | 326 | [https://www.jonobacon.com/2012/07/25/building-strong-community-structural-integrity/|drive-by |
| 326 | 327 | contributions]. Fossil's closest equivalent is its unique |
| 327 | 328 | [/help?cmd=bundle|bundle] feature, which requires higher engagement |
| 328 | - than firing off a PR.⁴ This difference comes directly from the | |
| 329 | + than firing off a PR.⁵ This difference comes directly from the | |
| 329 | 330 | initial designed purpose for each tool: the SQLite project doesn't |
| 330 | 331 | accept outside contributions from previously-unknown developers, but |
| 331 | 332 | the Linux kernel does.</p></li> |
| 332 | 333 | |
| 333 | 334 | <li><p><b>No rebasing:</b> When your local repo clone syncs changes |
| @@ -670,10 +671,16 @@ | ||
| 670 | 671 | static elements of the web site served via D. Richard Hipp's own |
| 671 | 672 | lightweight web server, |
| 672 | 673 | <tt>[https://sqlite.org/docsrc/doc/trunk/misc/althttpd.md|althttpd]</tt>, |
| 673 | 674 | which is configured as a front end to Fossil running in CGI mode on |
| 674 | 675 | these sites. |
| 676 | + | |
| 677 | + <li><p>That estimate is based on pricing at Digital Ocean in | |
| 678 | + mid-2019: Fossil will run just fine on the smallest instance they | |
| 679 | + offer, at US $5/month, but the closest match to GitLab's minimum | |
| 680 | + requirements among Digital Ocean's offerings currently costs | |
| 681 | + $40/month. | |
| 675 | 682 | |
| 676 | 683 | <li><p>We have yet to hear from someone who has ported Fossil to |
| 677 | 684 | [https://en.wikipedia.org/wiki/Z/OS|z/OS], for example, though it |
| 678 | 685 | should be quite possible. |
| 679 | 686 | |
| 680 | 687 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -127,14 +127,15 @@ | |
| 127 | [https://about.gitlab.com/|GitLab], a third-party extension to Git |
| 128 | wrapping it in many features, making it roughly Fossil-equivalent, |
| 129 | though [https://docs.gitlab.com/ee/install/requirements.html|much more |
| 130 | resource hungry] and hence more costly to run than the equivalent |
| 131 | Fossil setup. GitLab's basic requirements are easy to accept when you're dedicating |
| 132 | a local rack server or blade to it, since that's about the smallest |
| 133 | thing you could call a "server" these days, but when you go to host that |
| 134 | in the cloud, you can expect to pay about 8⨉ as much to comfortably host |
| 135 | GitLab as for Fossil. This difference is largely due to basic |
| 136 | technology choices: Ruby and PostgreSQL vs C and SQLite. |
| 137 | |
| 138 | The Fossil project itself is [./selfhost.wiki|hosted on a very small |
| 139 | VPS], and we've received many reports on the Fossil forum about people |
| 140 | successfully hosting Fossil service on bare-bones $5/month VPS hosts, |
| @@ -207,11 +208,11 @@ | |
| 207 | facilities Fossil needs to do its thing. (Network sockets, file locking, |
| 208 | etc.) There are certainly well-known platforms Fossil hasn't been ported |
| 209 | to yet, but that's most likely due to lack of interest rather than |
| 210 | inherent difficulties in doing the port. We believe the most stringent |
| 211 | limit on its portability is that it assumes at least a 32-bit CPU and |
| 212 | several megs of flat-addressed memory.³ Fossil isn't quite as |
| 213 | [https://www.sqlite.org/custombuild.html|portable as SQLite], but it's |
| 214 | close. |
| 215 | |
| 216 | About half of the code in Fossil is actually an embedded copy of the |
| 217 | current version of SQLite. Much of what is Fossil-specific after you set |
| @@ -323,11 +324,11 @@ | |
| 323 | [https://www.git-scm.com/docs/git-request-pull|pull requests] offer |
| 324 | a low-friction path to accepting |
| 325 | [https://www.jonobacon.com/2012/07/25/building-strong-community-structural-integrity/|drive-by |
| 326 | contributions]. Fossil's closest equivalent is its unique |
| 327 | [/help?cmd=bundle|bundle] feature, which requires higher engagement |
| 328 | than firing off a PR.⁴ This difference comes directly from the |
| 329 | initial designed purpose for each tool: the SQLite project doesn't |
| 330 | accept outside contributions from previously-unknown developers, but |
| 331 | the Linux kernel does.</p></li> |
| 332 | |
| 333 | <li><p><b>No rebasing:</b> When your local repo clone syncs changes |
| @@ -670,10 +671,16 @@ | |
| 670 | static elements of the web site served via D. Richard Hipp's own |
| 671 | lightweight web server, |
| 672 | <tt>[https://sqlite.org/docsrc/doc/trunk/misc/althttpd.md|althttpd]</tt>, |
| 673 | which is configured as a front end to Fossil running in CGI mode on |
| 674 | these sites. |
| 675 | |
| 676 | <li><p>We have yet to hear from someone who has ported Fossil to |
| 677 | [https://en.wikipedia.org/wiki/Z/OS|z/OS], for example, though it |
| 678 | should be quite possible. |
| 679 | |
| 680 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -127,14 +127,15 @@ | |
| 127 | [https://about.gitlab.com/|GitLab], a third-party extension to Git |
| 128 | wrapping it in many features, making it roughly Fossil-equivalent, |
| 129 | though [https://docs.gitlab.com/ee/install/requirements.html|much more |
| 130 | resource hungry] and hence more costly to run than the equivalent |
| 131 | Fossil setup. GitLab's basic requirements are easy to accept when you're dedicating |
| 132 | a local rack server or blade to it, since its minimum requirements are |
| 133 | more or less a description of the smallest |
| 134 | thing you could call a "server" these days, but when you go to host that |
| 135 | in the cloud, you can expect to pay about 8⨉ as much to comfortably host |
| 136 | GitLab as for Fossil.³ This difference is largely due to basic |
| 137 | technology choices: Ruby and PostgreSQL vs C and SQLite. |
| 138 | |
| 139 | The Fossil project itself is [./selfhost.wiki|hosted on a very small |
| 140 | VPS], and we've received many reports on the Fossil forum about people |
| 141 | successfully hosting Fossil service on bare-bones $5/month VPS hosts, |
| @@ -207,11 +208,11 @@ | |
| 208 | facilities Fossil needs to do its thing. (Network sockets, file locking, |
| 209 | etc.) There are certainly well-known platforms Fossil hasn't been ported |
| 210 | to yet, but that's most likely due to lack of interest rather than |
| 211 | inherent difficulties in doing the port. We believe the most stringent |
| 212 | limit on its portability is that it assumes at least a 32-bit CPU and |
| 213 | several megs of flat-addressed memory.⁴ Fossil isn't quite as |
| 214 | [https://www.sqlite.org/custombuild.html|portable as SQLite], but it's |
| 215 | close. |
| 216 | |
| 217 | About half of the code in Fossil is actually an embedded copy of the |
| 218 | current version of SQLite. Much of what is Fossil-specific after you set |
| @@ -323,11 +324,11 @@ | |
| 324 | [https://www.git-scm.com/docs/git-request-pull|pull requests] offer |
| 325 | a low-friction path to accepting |
| 326 | [https://www.jonobacon.com/2012/07/25/building-strong-community-structural-integrity/|drive-by |
| 327 | contributions]. Fossil's closest equivalent is its unique |
| 328 | [/help?cmd=bundle|bundle] feature, which requires higher engagement |
| 329 | than firing off a PR.⁵ This difference comes directly from the |
| 330 | initial designed purpose for each tool: the SQLite project doesn't |
| 331 | accept outside contributions from previously-unknown developers, but |
| 332 | the Linux kernel does.</p></li> |
| 333 | |
| 334 | <li><p><b>No rebasing:</b> When your local repo clone syncs changes |
| @@ -670,10 +671,16 @@ | |
| 671 | static elements of the web site served via D. Richard Hipp's own |
| 672 | lightweight web server, |
| 673 | <tt>[https://sqlite.org/docsrc/doc/trunk/misc/althttpd.md|althttpd]</tt>, |
| 674 | which is configured as a front end to Fossil running in CGI mode on |
| 675 | these sites. |
| 676 | |
| 677 | <li><p>That estimate is based on pricing at Digital Ocean in |
| 678 | mid-2019: Fossil will run just fine on the smallest instance they |
| 679 | offer, at US $5/month, but the closest match to GitLab's minimum |
| 680 | requirements among Digital Ocean's offerings currently costs |
| 681 | $40/month. |
| 682 | |
| 683 | <li><p>We have yet to hear from someone who has ported Fossil to |
| 684 | [https://en.wikipedia.org/wiki/Z/OS|z/OS], for example, though it |
| 685 | should be quite possible. |
| 686 | |
| 687 |