Feedback to author: The diagram and explanation took a beat longer than normal to scan, since this buries a bit that it’s not about the beautiful source control system called fossil shipped as a composition of modules: https://fossil-scm.org/home/doc/trunk/www/index.wiki Great diagrams, so of course that’s the first thing a reader will skim. People biuld things based on git all the time, the diagram looks like…

– Source: Hacker News
/
8 months ago

There are (all too rare) tools that back those objects with git as well. And there’s always fossil … https://fossil-scm.org/home/doc/trunk/www/index.wiki But it’s not git. :-(.

– Source: Hacker News
/
11 months ago

I don’t think git should be the infrastructure of collaboration. It’s good for long-lived artifacts, but isn’t good for discussion, for rights management, … Fossil (https://fossil-scm.org/home/doc/trunk/www/index.wiki) is of course better, but if git must remain, I believe the base infrastructure should be the mailing list. Patches, branches and releases can live inside a mailing list, it is naturally built for…

– Source: Hacker News
/
about 1 year ago

Have you spent much time using Fossil? https://fossil-scm.org/home/doc/trunk/www/index.wiki.

– Source: Hacker News
/
about 1 year ago

> To make things more complicated, they also use their a relatively niche version management system instead of git. Which would complicate making contributions (if they accepted them). The Fossil VCS actually has a page explaining why it was created, instead of just using Git: https://sqlite.org/whynotgit.html Honestly, a lot of those points make sense, especially how Git is perhaps a little bit more complex and…

– Source: Hacker News
/
over 1 year ago

Or https://fossil-scm.org/home/doc/trunk/www/index.wiki if you don’t mind learning some new commands.

– Source: Hacker News
/
over 1 year ago

For the most part there’s really only the built-in docs as it never really got popular (which I suspect is largely due to the opinionated take on Cathedral vs Bazaar use-cases).

Source:
over 1 year ago

There was still CVS/RCS. They both suck in comparison svn, which sucks in comparison to git (which itself sucks in comparison to fossil; if only fossil wasn’t quite so tightly bound to cathedral model…), but they were around.

Source:
over 1 year ago

Related: You can use the Fossil bug tracker as a generic SQLite table. You can modify the interface for any type of input. While you can edit the schema if you want to use it as a traditional SQL database, I’ve found it easiest to treat one of the text columns as JSON and do queries on that. The advantages: You get a web interface for free (using CGI) if you want one, it’s distributed and version controls your…

– Source: Hacker News
/
over 1 year ago

Fossil, the web ui for the version control system. It is a single statically linked binary that is also used as the command-line tool. It is truly simple. No pile of dependencies or external database to maintain or any other complexities.

Source:
almost 2 years ago

Fossil SCM (https://fossil-scm.org/home/doc/trunk/www/index.wiki) It’s almost like Git + Gitea, all in a single application. Code + tickets + wiki + notes all version controlled and capable of hosting the server itself. Also, the repo is just a SQLite database, so backup is easy.

– Source: Hacker News
/
over 2 years ago

Fossil could be one of them. https://fossil-scm.org/home/doc/trunk/www/index.wiki.

– Source: Hacker News
/
over 2 years ago

I’m inclined to look at tools like fossil again, for it’s distributed issue tracking and wiki capability https://fossil-scm.org/home/doc/trunk/www/index.wiki.

– Source: Hacker News
/
over 2 years ago

Also, I don’t think you can separate having effective backups from having organized files to begin with. Instead of going full github, take a look at Fossil SCM (https://fossil-scm.org/home/doc/trunk/www/index.wiki).

Source:
over 2 years ago

I have been kicking the tires on Fossil, lately, https://fossil-scm.org/home/doc/trunk/www/index.wiki which incorporates an embedded http server. It lets you create content through your browser, via a wiki interface.

Source:
over 2 years ago

The Sqlite/Fossil website, although not written in SQL, the entirety of it is a single sqlite/fossil db.

Source:
almost 3 years ago

I don’t know, why automated bots classified my question as spam on r/Development, maybe because of a link here, but I am looking for every useful hint, and every full answer in the research for integrated solutions crafted for single developers. Up to now I have found only two, it’s Bazaar in Solo mode and Fossil. So does anyone know others?

Source:
about 3 years ago

I contend that Americans need to rise up and require a government that makes federal legislative and tax “code” visible through a read-only fossile[1] repository. Maybe a state alcan lead the way. For non-classified discussion, the fact that we are paying customers and aren’t privy to the who/what/where/when/why of these important decisions is just last-century. [1]…

– Source: Hacker News
/
about 3 years ago

Fossil – distributed version controls system
Https://fossil-scm.org/home/doc/trunk/www/index.wiki.

Source:
over 3 years ago

I’m not aware of any Git-based one, but that’s sort of the intent behind Fossil. A Fossil repo contains not just code, but also bug tracking, wiki, forums, etc.

Source:
over 3 years ago

If you just want to use for personal single-person projects fossil [1] and mercurial [2] may be a better choice, given both comes with in-built web interface. Just run hg serve or fossil server or fossil ui. No need any external platform or program. [1] https://fossil-scm.org/home/doc/trunk/www/index.wiki [2] https://www.mercurial-scm.org/.

– Source: Hacker News
/
over 3 years ago