I currently run a personal wiki for some notes, recipes, and stuff. It’s set up using Wiki.js as the server. I’m the only regular user, and I feel like it’s a bit of an overkill.
Does someone have any suggestions for a more lightweight wiki server? I tried DokuWiki and mostly like it. But the UI is very old and dare I say, ugly. I love the UI of Wiki.js btw.
My main criteria is that it should be lightweight. I don’t need fancy editing features. Happy to work with raw html or markdown files.
I need some kind of permission management to hide some private wikis from the public, but otherwise I don’t really care.
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
I use tiddlywiki for my single-user wiki. The setup is dead simple, one html file on your computer you open directly. There is also a nodejs server implementation, which I use.
I needed something dead-simple to keep homelab documentation. If it’s not simple, I probably wouldn’t keep up with changes. I landed on An Otter Wiki https://github.com/redimp/otterwiki
I use markdown files in git + mkdocs with a post-commit build and push step. You could also try lektor.
I’ve been using silverbullet.md
Its more notes than wiki I guess so depends what you’re after.
I use gitit and it’s already packaged in most Linux distros.
Dokuwiki doesn’t have to look old, it is only the default theme that does. Just install a nicer theme and the Prosemirror addon and it looks and functions like any other modern wiki.
You said you liked the look of wiki.js but didn’t say what you didn’t like (unless I was missed it). Why not just use wiki.js? If you want permissions you’ll likely end up with other features like editing too.
I currently use Wiki.js but it’s a bit too much. The image size is around 500MB. I don’t see why I need such a huge program for hosting essentially text files and some images.
From the comments, DokuWiki with a modern theme, Fossil-SCM, and MkDocs seem nice. I’ll probably try some of these during the weekend.
@SexualPolytope
For a long time I’ve used https://tiddlywiki.com/ for tracking details and notes while working on projects.
#wiki
Mkdocs fits your criteria imo. But if you want something more customizable, you could use the astro.build docs template
It’s apparently early in development, but there’s an ActivityPub implementation of wikis made by one of Lemmy’s dev.
Using dokuwiki, just cut the cheese for me.
Its “old” because it uses php, but its quite solid and doesn’t need a database, so all plus to me.
There are cool and modern looking themes too.
I second DokuWiki. It’s super lightweight and infinitely customizable with plugins.
I use https://mycorrhiza.wiki/ it is not very fancy but it is a single executable file and stores pages in a git repository, so no database is needed and doing the export is as simple as reading some files.
Trilium. Share the nodes in the tree that you want public.
Mediawiki
+1.
And if you truly need lightweight,
Dokuwiki
I just left Docuwiki for Notion but i used Dokuwiki for almost 10 years and it was perfect for simple documentation.
I have been using Bookstack, I like it though it is missing a few features I would love:
Seconding Bookstack. I’ve embedded videos in it and I don’t recall anything special to do it. I also think there’s a way to comment on specific pages…mostly because I remember disabling that functionality.
Agreed on the roles and permissions aspect though. It’s pretty standard to do that for bigger deployments, but it may be a bit overkill for a single user instance.