WelcomeUser Guide
ToSPrivacyCanary
DonateBugsLicense

©2026 Poal.co

106
So I recently got into Docker and spun up a self hosted wiki.js container to house personal documentation and another for lore/world building info for a TTRPG game I run. Was using wiki.js a mistake? It was super easy to setup, but looking at the GitHub the project seems dead. If the next major version ever does come out it looks like it'll be a total rewrite AND a database change. I don't want to populate them with content just to have it get all fucked up down the line, or get jammed up by an unlatched security vulnerability. Should I switch to another wiki software? If so, any recommendations?

So I recently got into Docker and spun up a self hosted wiki.js container to house personal documentation and another for lore/world building info for a TTRPG game I run.

Was using wiki.js a mistake? It was super easy to setup, but looking at the GitHub the project seems dead. If the next major version ever does come out it looks like it'll be a total rewrite AND a database change. I don't want to populate them with content just to have it get all fucked up down the line, or get jammed up by an unlatched security vulnerability.

Should I switch to another wiki software? If so, any recommendations?

Yes
No, development is just glacial
Fuck You!

(post is archived)

[–] 1 pt

Can you export to JSON or XML for possible import into another system? The problem always is lock in, especially if you never know if the devs throw in the towel or sell out.

[–] 0 pt

It looks like I can export to markdown files.

I ended up installing xwiki. It's big and kinda slow but it works just fine. I think I'll use it going forward. I might keep my wiki.js container going for my personal documentation, or I might just set up obsidian sync. I'm not too picky where my documentation lives.