Reading collection

Self-Hosted Wiki: BookStack, DokuWiki and MediaWiki

Pick a self-hosted wiki for a team or homelab and measure editing, search, access, export, and recovery using real documentation tasks.

Editorial update

Decision in brief

Choose BookStack if your team wants a hierarchical handbook with browser editing and content roles. Choose DokuWiki for a small, file-backed reference where you value a simple storage model. Choose MediaWiki if you plan to maintain an encyclopedia-style site with template reuse and experienced wiki editors. Choose by author and reader tasks, and test a readable export alongside server recovery.

Pick a wiki: BookStack — Handbooks. DokuWiki — File storage. MediaWiki — Templates.
Test search, editing permissions and a readable export with ten representative pages.

Choose by how people write, organize, and recover pages

Some teams want a shelf of ordered manuals with owners. Others need freeform linked pages or repeated templates. Compare how a non-admin editor adds a page, how a reader finds the current version, and which users may see private material. Content exports or source pages may omit permissions, attachments, or application configuration.

Plan for two outcomes after failure. A service restore retains the application and its behavior. A plain reading copy lets someone get the essential instructions if the service never comes back. Keep the infrastructure runbook and the steps to find backups available outside the wiki.

OptionGood starting pointOperational check
BookStackStructured handbook with browser editing and delegated rolesRestore database, uploaded files and the configuration key. Check inheritance with an ordinary user.
DokuWikiSmall wiki with file-based storage and namespace organizationRecover content, media, settings and extensions and verify the reader can find an original page.
MediaWikiCross-linked encyclopedia or template-rich referenceCapture database, uploads, extensions and server configuration as a consistent recovery set.

Two HN workflows illustrate the value of a readable copy

unethical_ban reported setting up DokuWiki with public and private sections and using it to record deployment procedures. For an operations wiki, turn access separation and finding the right runbook into explicit acceptance checks for normal users.

inanutshellus reported that after a family MediaWiki server died, backups existed but nobody in the family would likely rebuild the application. Pick an archive format someone other than the operator will actually open, then test that handoff with a reader unfamiliar with the setup.

Measure search, authorship, and handoff with ten pages

Choose ten representative pages, including one restricted runbook, a linked procedure, a page with an attachment, and two pages readers often confuse. Invite an editor and an ordinary reader.

  1. Create and rename a page, link to it from two others, and restore a prior revision. Check the attachment links after rename and record how much help the editor needed.
  2. Have the reader find five answers from realistic search queries without an exact title. Run the same test with a restricted role and check that sensitive pages, link previews and attachments are unavailable to that role.
  3. Export critical pages and have a second person open them off the server. Restore the full backup to a blank environment, checking page counts, attachments, history and access rules separately.
  4. Approve if every required privacy check passes, readers find at least four of five answers within two minutes each, and recovery meets your time target. If readers miss answers, correct titles and structure and retest before migrating.

Related articles