Good old DokuWiki[1] has few dependencies (not even a database), is super easy to set up without Docker and comes with a zillion useful plugins. Its wiki markup format is supported both for import and export by pandoc.<p>Just saying...<p>[1] <a href="https://www.dokuwiki.org/" rel="nofollow">https://www.dokuwiki.org/</a>
If anyone is after a different approach, or alternative requirements, I've been working on BookStack [1] for the last few years in my free time.<p>[1] <a href="https://www.bookstackapp.com/" rel="nofollow">https://www.bookstackapp.com/</a>
The self-hosted requirements are pretty hefty.<p>Node.js >= 12
Postgres >=9.5
Redis >= 4
AWS S3 storage bucket for media and other attachments
Slack or Google developer application for authentication<p>Requiring Postgres and Redis for a documentation site seems overkill. Also not a fan of requiring S3, an option to save the media to the local disk would be nice. This seems somewhat over-engineered for a knowledgebase, especially when some of the competition has no runtime requirements other than a webserver (DokuWiki, statically generated Gatsby/Hugo sites). And I can still get Slack notifications on edit from MR notifications.