Wiki.js
otsumami.wikijs
Wiki platform with a WYSIWYG and Markdown editor, page versioning, granular permissions and optional two-way synchronisation of content with a Git repository.
A Docker Compose file for Wiki.js alone, generated from the catalog and checked by the safety inspector. Sign in and use Kitchen Credits to activate it.
Uses the Medusa cart and payment-session path. This test control does not create an order or capture payment.
Wiki.js stores pages in a database while optionally mirroring them to a Git repository in both directions, so content can be edited in the browser or committed as files and stay consistent either way. Several editors are available per page — visual, Markdown, plain HTML and AsciiDoc — with full version history and diffs between revisions. Permissions are rule-based across page paths and user groups, and authentication can come from local accounts or an external identity provider. A first deployment completes the setup wizard, creates the administrator account and publishes one page.
You know it worked when
- The setup wizard completes and the administrator can sign in.
- A page created in the editor renders at its configured path.
- An edit produces a new version with a viewable diff against the previous one.
- A permission rule blocks an unauthorised group from a restricted path.
- With Git synchronisation enabled, a page edit appears as a commit in the repository.
Known sharp edges
- The setup wizard runs unauthenticated on first start, so the instance must not be publicly reachable before the administrator account is created.
- An external database must be running and reachable before the container starts, or setup fails rather than waiting.
- Git synchronisation resolves conflicts by overwriting in one direction, so simultaneous edits in the browser and the repository can lose content.
- The pinned 2.x line has been in maintenance while a rewritten 3.0 has remained unreleased for an extended period, so new feature work is not arriving.