Welcome • User Guide
ToS • Privacy • Canary
Donate • Bugs • License

©2026 Poal.co

973
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)

You are currently inside a comment thread.
Click here to see all the comments (7).
[–] • 1 pt

I use mediawiki (mediawiki.org)

[–] • 1 pt

I started with mediawiki but kept getting database authentication errors even though I was defining the root and user pass in the compose file. Frustration with that led me to wiki.js and I was up and running in about 10 minutes.

Maybe I just need to take another run at it.

[–] • 0 pt

I run it in a docker container and have never had an issue with it. Setup took a few mins and I havn't had an issue since install a few years ago.