Me too. My case is a little different though. I realized the tickets database is a generic sqlite database you can use as you wish, but comes with a web server, syncing, and version control out of the box. It was simple to create a CGI app in my language of choice that gave me a web interface to my notes system but without having to implement my own authentication. If I want to work locally using Emacs, I can. If I want a full or partial backup in text format, it's a regular sqlite dump of the tickets database.
E.g. I can't find a way to add files/images/make commits in the UI at all. I can make wiki pages or tickets in there (honestly, the wiki probably covers 99% of what I want, aside from it not being very streamlined to say the least), but I haven't found a way to add files except via `fossil add` on the CLI. Have I just missed it?
Otherwise, the main things keeping me from being more interested is that it's a large blob -> harder to sync, and there don't seem to be any mobile-friendly implementations (e.g. no app that just runs it). A folder of markdown files and images/etc to embed via `` is dramatically easier and more flexible on both of those fronts... but I do miss having a history.
It won’t be difficult to build a mobile friendly web UI on fossil server if you want a complete mobile experience.
The wiki has had some work done to it in recent versions, it has preview now for instance.
Fossil syncs *FOR* you. let fossil handle syncing, that is it's bread and butter.
But yes, you have a good point - once you have a server running, syncing is very efficient.
But yes I agree.
You can just copy/overwrite the SQLITE DB file, and do a bulk replace. Not the same as 2-way sync that Fossil will give you, obviously.
The data format is literally a SQLITE DB, which is the most used DB on the planet.
Binaries are available for all the major OS's and many "alternative" ones.
I use Fossil-SCM for my personal notes. Works great. I even run many websites with Fossil-SCM as the wiki is fabulous for a super easy to deploy and super easy to edit website, even if there is zero code in the VCS portion.
I also use fossil on USB sticks for my legal information on my death. I include fossil binaries for every platform, so whenever I'm dead my next of kin can just plug in the USB stick I update every year and hand to them and double click and boom, fossil-scm opens with a VCS of all my files and documents, financials, etc, a wiki with next steps, etc. Easy peasy, and they get everything they need to take care of all the stuff to handle my estate, in a nice easy to use manner, with basically no work on my part.