https://github.com/pgilbertschmitt/briki
Personal wiki written in TypeScript React, running on Electron
https://github.com/pgilbertschmitt/briki
Last synced: 2 months ago
JSON representation
Personal wiki written in TypeScript React, running on Electron
- Host: GitHub
- URL: https://github.com/pgilbertschmitt/briki
- Owner: PGilbertSchmitt
- License: mit
- Created: 2020-06-06T16:42:49.000Z (almost 5 years ago)
- Default Branch: master
- Last Pushed: 2023-01-07T06:36:56.000Z (over 2 years ago)
- Last Synced: 2025-01-17T14:39:06.065Z (4 months ago)
- Language: TypeScript
- Size: 844 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 14
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Briki, a Brisk Wiki reader (??)
Okay, so I wanted a Wiki-reading application that used simple Markdown. Maybe I realized that I don't need to save it as a sqlite file. Maybe that already exists and I'm just making this for fun. Maybe it's none of your business.
This application can read a directory tree and render Markdown files. That's it. Maybe one day I'll allow it to edit files as well, or add support for other markups, but for now, I'm not interested. I'm creating this to make it easy to read a "Wiki" that's just several Markdown files in a trenchcoat. VSCode's Markdown preview isn't very wieldy for that.
With that out of the way, what else is there to say?
## Development
If you're trying to run this yourself (or you're just me from the future and forgot how to get around this), you may run into this issue while trying to run locally:
```
[23071:0215/145228.085420:FATAL:setuid_sandbox_host.cc(158)] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /home/gilbert/dev/Briki/bin/linux-unpacked/chrome-sandbox is owned by root and has mode 4755.
```
What does this mean? I don't really have all that much of a clue. However, I did run into this [Github thread](https://github.com/electron/electron/issues/17972) on the Electron repo, which didn't really help all that much in my understanding. Nevertheless, I got past it with `sudo sysctl -w kernel.unprivileged_userns_clone=1`.