3 ms·

I've been using Fossil as my own personal knowledge repository for a few months, and it's been wildly successful. It's pretty much Gitea in a single SQLite fil

I've been using Fossil as my own personal knowledge repository for a few months, and it's been wildly successful. It's pretty much Gitea in a single SQLite file (Wiki, tickets, version control, etc.). It's weird, but you can edit all of these things off-line and then sync everything back. `fossil ui` hosting the server for my docs locally, and from my home server is super useful and easy. Some of the commands are super weird though, but I put them my homepage of my fossil docs :) The auto-sync feature helps since I work on multiple computers to help ensure that I don't get too far out of sync.

olav 5y ago
This is actually the use case I have in mind when I think of moving my personal knowledge management system knowfox to something more enduring like fossil. It currently is built on php/mysql with laravel with a web ui in bootstrap. This has become super annoying for a few years now because once a year or so I have to port it to a new version of laravel and cope with the new javascript framework du jour that it now promotes. This would be fine, of course, if you run an agency which extracts money from clients for continuous upgrades, but not for a personal project. Fossil, on the other hand, is built for longevity. It is a single executable and comes with all tools built in.