Repository navigation
No way to read the wiki locally as a wiki — only as raw markdown #3
Description
Activity
- added a commit that references this issue
on Aug 26, 2026 Solved in #4 (squash-merged as 67e7b3f).
docker compose up -din a fresh clone now brings up Wiki.js 2.5 with PostgreSQL, serving
this repository's pages at http://localhost:3000, readable with no login.WIKI_PORT
overrides the port when 3000 is taken.All four points from the issue:
- One command, no wizard.
wikijs/bootstrap.pycompletes Wiki.js's setup over its own
APIs —POST /finalizefor the wizard, GraphQL for the rest. It runs once, exits, and is
idempotent, so re-running is also the reload command. - Every page present. The Local File System target is pointed at the mounted repository
and imported. 8 pages; README is dropped afterwards since it documents the repository
rather than the project. - Guests read anonymously. Verified and granted on every run.
- Automated check.
tools/check_wikijs.py, run in CI against a real stack.
Two design points worth recording:
The checkout is mounted read-only and the disk target is disabled again after importing.
It is a push target — left enabled, Wiki.js would try to write edits back into whoever's
working tree. Importing is all that is wanted from it.The check does not follow redirects. My first version passed a fully locked-down wiki:
Wiki.js answers an unauthorised guest with a302to/login, urllib followed it, and the
login page returns200carrying the site title — so the assertion matched. A3xxis now
the failure it actually is. Verified by revoking guest read: all 8 pages fail, and re-running
bootstrap restores them.Verified on Wiki.js
2.5.314. Both CI jobs pass, including the stack coming up from scratch.- One command, no wizard.
Cloning this repository gets you Markdown files.
tools/serve.pyrenders them for review,but it is a preview shim, not the thing the content is actually published into.
There is no way to run the real target — Wiki.js — against this repository's content, so
nobody can check how a page will actually look, and nobody can browse the wiki offline.
Expected once solved
docker compose up -din a fresh clone brings up a self-hosted Wiki.js serving thisrepository's pages, browsable immediately with no login.
Specifically: