I installed MediaWiki on a server three years ago for a project and I really liked it! It was nice using software that thousands of other people had already gone through the pain of trying out.
I got rid of it because I didn’t want to keep maintaining a cloud server. If anybody’s got a CF stack for AWS that sets up a serverless MediaWiki, hit me up. I’d love to try it out.
I am in the process of setting up MediaWiki Fort personal content (personal kB) and I’m using the official docker image. It’s very ergonomic.
I actually use TiddlyWiki and find that it’s more than adequate.
I gave that a small try and it didn’t feel like the right fit for me. Still a nice idea though.
It’s not AWS but I did find a gist about setting it up on Heroku. Might be something to look into
After I posted my comment I started thinking about various ways to accomplish this. The easiest would probably be a container deployment used only as-needed on a spot-bid basis with a budget. This heroku solution looks really cool also. There’s probably a much harder way to do it without instances at all, and it might make for a great blog post, but I don’t have the necessary motivation to chase it down. I really love the tool, though. It’s amazing that such tools are free.
I recall setting up MediaWiki years ago and loving it! Really like the idea of a personal Wiki fro this kind of thing - currently using SimpleNote but it’s pretty limiting, maybe I’ll give MediaWiki a go.
At the beginning, I wasn’t all that impressed or optimistic about MediaWiki simply because of how dated it looks. After exploring more and seeing what it’s actually capable of, I don’t know how I ever lived without it ;) All of what I’m documenting is for NixNet and MediaWiki is perfect but I’ve also started trying to maintain a Zettelkasten as more of a personal knowledge base. It’s only been a few weeks and I haven’t had much to write outside of documentation but it seems like it’ll work pretty well.
I used to have a MediaWiki instance about a decade ago document processes here around the farm for use by various official instances who like to have things documented (in triplicate, lost, found again, stored in a disused cabinet for a few months, then buried under a layer of peat to be used for domestic heating purposes). I got quite a bit of wiki spam until I closed of all editing for non-logged-in users - and still some spammers managed to add content. The spammers kept on trying and they still keep hitting the domain even though the wiki has been offline for close to 3 years now. Things might be better now but back then it was easy to end up with a spam-ridden stinking pile of excrement instead of a useable wiki.
I feel like allowing self-service-sign-up for any ‘in house’ system leads quickly to spam. OTOH, I’ve had zero trouble from the systems I run where I manually provision accounts (other than being bothered for accounts).
That was the thing, account registration was closed. The spammers must have used a bug to get access.