We used Dokuwiki in a similar situation. It's been a few years since I last used it (new client uses confluence) but I remember it was super easy to connect external tools. If your script can output text, Dokuwiki can display it :)
I have a docuwiki running on RPi at home (files are stored on a USB-connected HDD) as a personal knowledge management system. It doesn't even need any DB, just stores it in text files. Took just a few minutes to set up. Doesn't get any simpler (other than using plain text files on local of course :)
Is this a good choice for a company? These sorts of "hacker" solutions inevitably fall flat because people want a bunch of bells and whistles and don't mind things like never being able to find anything (arguably the single most important feature of a wiki) or being able to integrate their documentation with other systems.
It integrated well with our LDAP server. Its search is great, and everything is plain text so you can do whatever you like. It has a rich text editor but you can also edit plain text.
Dokuwiki has been my go-to solution for docs everywhere I've been for the past ten years or so unless they already have a (usable) wiki in place.
Trivial to set up. Trivial to migrate to, and from (should you ever need to). Doesn't need a database. There are lots of plugins available and it's sooo easy to write plugins for. Even if you hate PHP.
I've stuck with Git based markdown wikis. Nice thing is that when the web app you were relying on enevitably dies the data format is portable.
Currently using Gitea's built in per-repo wiki as a general wiki after we migrated from Gitlab to self hosted Gitea. As a bonus there's no maintenance burden, Gitea itself has super low maintenance burden, single portable binary (I use an APT repo), single config. Latency of Navigating Gitea is also instant by comparison to Gitlab which was driving us nuts it's so slow.
I tried to run Wiki.js in the past but it's really buggy and has a lot of spinners/loading pages for what is supposed to be simple html pages so i've been looking for a good self-hosted alternative since.
I love how there are so many options in the HN comments, and some of them look really good as well, however I still struggle to believe that none of them are self-contained. All of them require a a redis container, a postgres container, a frontend proxy etc.. for a simple wiki? can't the wiki run it's own redis-cache internally, maybe run with sqlite? Have all the oauth/proxy stuff optional?
In the meantime i've been running with mkdocs but since it's a site generator but it's not really user friendly as you need to redeploy to see changes, etc..
You're looking for Dokuwiki. It doesn't even need a database; pages are stored as plain text files on disk. Its appearance is a little dated, but it seems to work very well.
MediaWiki. Is there something wrong with the solution powering Wikipedia? It’s very simple to set up, and you can one-click deploy it on DigitalOcean for $10/month.
I gave MediaWiki a shot just now but it's seriously lacking Markdown support. Seems that there's a plugin for it but that's a no-go in the docker setup, would need to make my own container because it depends on some php package that doesn't come in the default image. Really a shame the docker setup isn't made to be extensions friendly.
Can highly recommend outline (https://www.getoutline.com/). You can self-host or opt for the hosted version. Built and maintained by one of the linear devs.
I've used Wiki.js for a while but was always annoyed of the loading times. It's just one of those applications that render everything in the client.
So I haven't stopped looking for other applications and when I tried BookStack I knew I found my solution: Loads amazingly fast, while running in the simplest environments as it's PHP.
Previously I have also used DokuWiki, which was also simple but I didn't want to write in Markdown, and especially explain it to others.
I cannot recall why i did not go for wiki.js myself, I tried, but I kept looking. Ended up with https://docmost.com/ and I've been quite happy. It's probably more equal to Notion then Wikipedia, but as a internal knowledge base it seem to be hit the right spot in terms simplicity and features.
I can't believe at this day, many products don't care about mobile viewing.
I thought it makes a big sense to write documents on PC and then view it elsewhere out there but developers don't seem to care about that usage.
Docmost makes tables completely unreadable on mobile having words wrap at the width of the device, especially when set as full-width which actually makes it even tighter for some odd reason.
Affine doesn't even support mobile at all and the GitHub issue about it is starting to age well.
AppFlowy does it the best of the bunch but it requires an app and it has minimal tablet support having only mobile app view than a native tablet view but at least it's usable having tables actually horizontally scroll as anyone would expect.
Outline isn't any better and a small test showed some weird behavior under mobile.
Readit News
https://www.dokuwiki.org/dokuwiki
EDIT: I decided to try dokuwiki in Podman, works nicely as long as you run:
https://www.redhat.com/en/blog/debug-rootless-podman-mounted...Trivial to set up. Trivial to migrate to, and from (should you ever need to). Doesn't need a database. There are lots of plugins available and it's sooo easy to write plugins for. Even if you hate PHP.
Currently using Gitea's built in per-repo wiki as a general wiki after we migrated from Gitlab to self hosted Gitea. As a bonus there's no maintenance burden, Gitea itself has super low maintenance burden, single portable binary (I use an APT repo), single config. Latency of Navigating Gitea is also instant by comparison to Gitlab which was driving us nuts it's so slow.
I love how there are so many options in the HN comments, and some of them look really good as well, however I still struggle to believe that none of them are self-contained. All of them require a a redis container, a postgres container, a frontend proxy etc.. for a simple wiki? can't the wiki run it's own redis-cache internally, maybe run with sqlite? Have all the oauth/proxy stuff optional?
In the meantime i've been running with mkdocs but since it's a site generator but it's not really user friendly as you need to redeploy to see changes, etc..
1. Does it support rendering OpenAPI json/yaml?
2. Also it seems like it supports Draw.io via public URL. That's a no go. Can it support draw.io diagrams via attachments?
3. Google drive support is nice. Do you plan on supporting OneDrive as well?
Does it support the use case of publishing the wiki as a public documentation site, while allowing authenticated users to edit?
Also, Dokuwiki is nice, if a little dated on the UI side of things.
https://www.bookstackapp.com/
https://fossil-scm.org/home/doc/trunk/www/wikitheory.wiki
That would solve so many problems.
So I haven't stopped looking for other applications and when I tried BookStack I knew I found my solution: Loads amazingly fast, while running in the simplest environments as it's PHP.
Previously I have also used DokuWiki, which was also simple but I didn't want to write in Markdown, and especially explain it to others.
https://www.bookstackapp.com/
I thought it makes a big sense to write documents on PC and then view it elsewhere out there but developers don't seem to care about that usage.
Docmost makes tables completely unreadable on mobile having words wrap at the width of the device, especially when set as full-width which actually makes it even tighter for some odd reason.
Affine doesn't even support mobile at all and the GitHub issue about it is starting to age well.
AppFlowy does it the best of the bunch but it requires an app and it has minimal tablet support having only mobile app view than a native tablet view but at least it's usable having tables actually horizontally scroll as anyone would expect.
Outline isn't any better and a small test showed some weird behavior under mobile.
Thanks for reporting the mobile table issue. I will have a look at it.
The fullwidth issue on mobile was recently reported. It will be fixed soon.
I appreciate your feedback.