Live data from Hacker News

How to setup self hosted wiki for your startup

themythicalengineer.com

21–30 of 87 posts

Re: How to setup self hosted wiki for your startup

#21
post #12

Can highly recommend outline ( https://www.getoutline.com/ ). You can self-host or opt for the hosted version. Built and maintained by one of the linear devs.

Agreed on outline, though their lack of local auth is kinda annoying. But Authelia works pretty great.

Re: How to setup self hosted wiki for your startup

#23
As much as I hate it, I think Confluence is the right choice for startups. (Or Github Wiki if you can stomach it). It's free to start, and you get 10 users. By the time you have 10 people who need access, (and you can export PDF's of pages if you have one off sharing to do) you pay $50/mo. If you have 10 employees $50/mo is pocket lint.

Re: How to setup self hosted wiki for your startup

#24
I ended up building my own Wiki in Go at some point, although I use this mainly for my own smaller purposes. Description and demo instance at:

https://wiki.gnoack.org/UkuleleWeb

It takes very little resources on my Raspberry Pi and is built to be extensible and safe through its transparent way of storing wiki pages as markdown files.

Re: How to setup self hosted wiki for your startup

#25
post #4

I tend to abuse fossil for it's wiki. Mainly because it is zero fuss to setup. https://fossil-scm.org/home/doc/trunk/www/wikitheory.wiki

I would have liked that too, except that I can't get oAuth integrated with fossil. That would solve so many problems.

Sit it behind oauth2-proxy?

Re: How to setup self hosted wiki for your startup

#28
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..

Re: How to setup self hosted wiki for your startup

#30

We used Dokuwiki in a similar situation. It's been a few years since I last used it (new client uses confluence) but I remember it was super easy to connect external tools. If your script can output text, Dokuwiki can display it :) https://www.dokuwiki.org/dokuwiki EDIT: I decided to try dokuwiki in Podman, works nicely as long as you run: podman unshare chown 1000:1000 /path/to/wiki/data https://www.redhat.com/en/bl…

Is this a good choice for a company? These sorts of "hacker" solutions inevitably fall flat because people want a bunch of bells and whistles and don't mind things like never being able to find anything (arguably the single most important feature of a wiki) or being able to integrate their documentation with other systems.
Post reply on HN