I want to document problems I run into and how I solve them. What offline tools or workflows would you recommend, preferably open source or self-hosted?
What do you use for an offline knowledge base?
Asked by
just-one-more-lap
Answers
Obsidian is worth a look if open source is a preference rather than a requirement. It keeps notes as Markdown files, so they're portable, and you can link related problems together.
You don't need to start with a pile of plugins. The basic setup is enough to write notes and connect them, and you can add extras later if you actually miss something.
Reply to this answer
If open source is a must, take a look at Logseq or Zettlr. Both are alternatives worth comparing for local notes. The more useful habit is writing down the fix soon after you find it, while the details are still fresh.
Reply to this answer
Honestly, a folder of Markdown files and Git is enough. Pick a folder structure that makes sense to you and use version control to track changes. You can edit the files with whatever editor you like, without committing to a particular knowledge base app.
some-assembly-possible:
Keeping the files locally also means you can look things up when your internet connection is down.
Reply to this answer
Zettel Notes is another option to check if syncing and encryption matter to you. Its built-in features may appeal more than adding plugins, though I'd compare it against your open-source requirement before choosing it.
Reply to this answer
For syncing across devices, RxDB is an option for an offline-oriented setup. That sounds like extra machinery for a simple personal notes folder, though, so I'd only investigate it if sync is a real requirement.
Reply to this answer
Add your answer
Answers are reviewed before publication.
just-one-more-lap:
Is there a simple format you'd use for each problem?
tiny victory parade:
Try a short description, the symptoms, what you tried, and the solution. Add links to related notes when one fix depends on another.