←back to thread

How to setup self hosted wiki for your startup

(themythicalengineer.com)
122 points sks147 | 1 comments | 17 Nov 24 08:14 UTC | HN request time: 0s | source
Show context
snozolli ◴[17 Nov 24 18:29 UTC] No.42165882[source]▶
you’ll need to increase the resources to atleast

"Atleast" isn't a word.

I looked at wiki.js and I don't understand why you wouldn't just install Mediawiki. It only takes a few minutes and wiki.js doesn't look any more sophisticated at a glance.

replies(2): >>42167221 #>>42167619 #
movedx ◴[17 Nov 24 21:03 UTC] No.42167221[source]▶
I agree. MediaWiki is a solid solution and is very easy to setup. You can one-click deploy on DigitalOcean for $10/month and just enable daily snapshots. You can even use a managed DB if you want.
replies(1): >>42168757 #
snozolli ◴[18 Nov 24 01:00 UTC] No.42168757[source]▶
You can one-click deploy on DigitalOcean for $10/month

Am I the only person left who simply has a web server? Untar Mediawiki, edit a few config variables, run an established database script, and off you go. Maybe I'm wildly out of touch, but I don't see why everything has to be a container or a monthly paid service around here.

I get it for something like an email server, where misconfiguration could lead to your server being a zombie, but I don't get it for something like a wiki.

replies(4): >>42169283 #>>42169541 #>>42171906 #>>42202669 #
1. Arrowmaster ◴[18 Nov 24 02:44 UTC] No.42169283[source]▶
Container makes it easy to update. I don't need to go read the instructions about which files I need to replace or what to do about modified files. If it's built properly to run from a container and uses sane version numbering, all I need to do is pull the new image and restart the container.

There are still plenty of not sane container builds that don't make it easy. If I need to checkout a git repo and mount a path into the container it's not sane. Pulling an image and starting a docker-compose should be all that's needed.