←back to thread

How to setup self hosted wiki for your startup

(themythicalengineer.com)
124 points sks147 | 1 comments | 17 Nov 24 08:14 UTC | HN request time: 0.236s | source
Show context
Fabricio20 ◴[17 Nov 24 20:14 UTC] No.42166791[source]▶
I tried to run Wiki.js in the past but it's really buggy and has a lot of spinners/loading pages for what is supposed to be simple html pages so i've been looking for a good self-hosted alternative since.

I love how there are so many options in the HN comments, and some of them look really good as well, however I still struggle to believe that none of them are self-contained. All of them require a a redis container, a postgres container, a frontend proxy etc.. for a simple wiki? can't the wiki run it's own redis-cache internally, maybe run with sqlite? Have all the oauth/proxy stuff optional?

In the meantime i've been running with mkdocs but since it's a site generator but it's not really user friendly as you need to redeploy to see changes, etc..

replies(3): >>42167195 #>>42167530 #>>42168218 #
movedx ◴[17 Nov 24 21:00 UTC] No.42167195[source]▶
MediaWiki. Is there something wrong with the solution powering Wikipedia? It’s very simple to set up, and you can one-click deploy it on DigitalOcean for $10/month.
replies(2): >>42168460 #>>42175809 #
jjmarr ◴[18 Nov 24 00:02 UTC] No.42168460[source]▶
MediaWiki doesn't have full WYSIWYG. The Visual Editor is nice, but doesn't support templates.
replies(1): >>42170247 #
bawolff ◴[18 Nov 24 06:30 UTC] No.42170247[source]▶
What do you mean by this? You can use templates when editing pages with mediawiki's visual editor.
replies(1): >>42248722 #
1. jjmarr ◴[26 Nov 24 18:55 UTC] No.42248722[source]▶
You're right. I was going to tell you about what a nightmare infoboxes are, but my experience is clearly out of date. I guess I'm used to a large public failure killing a project. I'm extremely impressed by the experience now and I shouldn't have commented without looking into it more.