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 :)<p><a href="https://www.dokuwiki.org/dokuwiki" rel="nofollow">https://www.dokuwiki.org/dokuwiki</a><p>EDIT: I decided to try dokuwiki in Podman, works nicely as long as you run:<p><pre><code> podman unshare chown 1000:1000 /path/to/wiki/data
</code></pre>
<a href="https://www.redhat.com/en/blog/debug-rootless-podman-mounted-volumes" rel="nofollow">https://www.redhat.com/en/blog/debug-rootless-podman-mounted...</a>
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.<p>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.<p>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?<p>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..
Can highly recommend outline (<a href="https://www.getoutline.com/" rel="nofollow">https://www.getoutline.com/</a>). You can self-host or opt for the hosted version. Built and maintained by one of the linear devs.
We tried many different wiki softwares before settling on Bookstack.<p><a href="https://www.bookstackapp.com/" rel="nofollow">https://www.bookstackapp.com/</a>
I tend to abuse fossil for it's wiki. Mainly because it is zero fuss to setup.<p><a href="https://fossil-scm.org/home/doc/trunk/www/wikitheory.wiki" rel="nofollow">https://fossil-scm.org/home/doc/trunk/www/wikitheory.wiki</a>
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.<p>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.<p>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.<p><a href="https://www.bookstackapp.com/" rel="nofollow">https://www.bookstackapp.com/</a>
I cannot recall why i did not go for wiki.js myself, I tried, but I kept looking. Ended up with <a href="https://docmost.com/" rel="nofollow">https://docmost.com/</a> 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.
As much as I hate it, I think Confluence is the right choice for startups. (Or Github Wiki if you can stomach it). It's free to start, and you get 10 users. By the time you have 10 people who need access, (and you can export PDF's of pages if you have one off sharing to do) you pay $50/mo. If you have 10 employees $50/mo is pocket lint.
For PHP/Laravel, there is an excellent wiki tool that I have used:<p><a href="https://www.bookstackapp.com/" rel="nofollow">https://www.bookstackapp.com/</a>
I ended up building my own Wiki in Go at some point, although I use this mainly for my own smaller purposes. Description and demo instance at:<p><a href="https://wiki.gnoack.org/UkuleleWeb" rel="nofollow">https://wiki.gnoack.org/UkuleleWeb</a><p>It takes very little resources on my Raspberry Pi and is built to be extensible and safe through its transparent way of storing wiki pages as markdown files.
Why not just use Google Drive or Office 365? You probably have one of them anyway, people know how to use it, and all the access control features are built in. Plus you can easily export all your docs and just put them on an ftp server in the worst case.
I'm kinda sad that there doesn't seem to be a thing that is basically Wikipedia-like but with Google Docs-like shared editing as a "canonical" open source offering in this space. Notion is too much stuff!<p>Basically want Confluence but faster.
I've been working on a plugin (Relay) [0] for Obsidian that makes it real-time collaborative. Obsidian has the perfect user experience for markdown wiki-style notes, but it was lacking the realtime collaboration. We use Obsidian+Relay internally every day and it is so so much nicer than Confluence, Notion, or Google docs -- plus it is super extensible so we can use additional plugins for Claude, mermaid.js, etc.<p>[0] <a href="https://obsidian.md/plugins?id=system3-relay" rel="nofollow">https://obsidian.md/plugins?id=system3-relay</a>
Think the popular tools out there like Notion often work well enough, the ease of use outweighs it's higher price for teams that look to expand.<p>If you want a free markdown based public wiki use Astro's Starlight.<p>A cheap private wiki can be made with Obsidian.
I like the idea of having a wiki be mostly serverless -- like lambda backed by s3.
A little searching found this:<p><a href="https://github.com/raboof/serverless-wiki">https://github.com/raboof/serverless-wiki</a>
Especially for small startups, <a href="https://typemill.net" rel="nofollow">https://typemill.net</a> can be a handy solution, since it is very lightweight and can also produce handbooks in PDF format.
All in all, this guide is pretty small. More of a solution overview than a guide. I would have appreciated if the steps in the "Making It Production-Ready" section were expanded upon, for example.
Another alternative that solves similar issues is Docusaurus: <a href="https://docusaurus.io/" rel="nofollow">https://docusaurus.io/</a>
<i>you’ll need to increase the resources to atleast</i><p>"Atleast" isn't a word.<p>I looked at wiki.js and I don't understand why you wouldn't just install Mediawiki. It only takes a few minutes and wiki.js doesn't <i>look</i> any more sophisticated at a glance.