Re:Foam: A personal knowledge management and sharing system ...
by ontouchstart on Thursday January 14, 2021 @05:02AM
(#25774468)
I run fossil-scm in docker-compose on local file system spin a server only for viewing and do the editing and CLI in VS Code.
It won’t be difficult to build a mobile friendly web UI on fossil server if you want a complete mobile experience.
Re:Foam: A personal knowledge management and sharing system ...
by zie on Thursday January 14, 2021 @03:42PM
(#25782191)
You can't add files or commits from the web UI.
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.
Re:Foam: A personal knowledge management and sharing system ...
by Groxx on Thursday January 14, 2021 @05:00PM
(#25783268)
Which requires running a fossil server that you can access anywhere, i.e. it has a custom and unique syncing system. That is... a rather significant requirement, compared to using a general file-syncing thing that you may already have.
But yes, you have a good point - once you have a server running, syncing is very efficient.
Re:Foam: A personal knowledge management and sharing system ...
by zie on Thursday January 14, 2021 @08:14PM
(#25785641)
Git's syncing system is custom and unique also.
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.
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.