in discussion Wiki Announcements and Proposals / Project Bulletin » Tech Notes
So I have good news, because for once I did not just claim to be working on wiki migration, but actually follow up by actually doing that.
So far I went through the process of actually setting up a MediaWiki instance on an nginx instance (instead of just messing with crappy local solutions) and frankly the process is quite simple. You just extract the MW provided archive, tell nginx where the root lies, and paste a ~20 lines config and that's pretty much it. However, I'll mention the two issues I ran into for the sake of posteriority anyway:
- Don't just apt install mediawiki; that package (at least on APT, idk how it is for AUR, flatpack, etc.) comes with an apache2 webserver that, during the APT installation process, is going for full on murderization of your beautiful, lightweight nginx server1. You can install MariaDB the necessary php dependencies manually, the Installation Requirements give you a handy overview of packages].
- I initially had problems actually running the wiki software because for some godforsaken reason, it was expecting a php8.1-fpm socket for cgi, whilst I had php8.4 installed. I tried messing around in the nginx config to adjust that path, but after some time I gave up and simply ln php8.4-fpm.sock php8.1-fpm.sock in /var/run/php. That surprisingly worked, even thought I never expected PHP to actually use semantic versioning. Could this cause nigh-undiagnosable errors down the line? Maybe. Probably less than having two concurrent PHP versions installed? Certainly.
So I guess my next step is to try that again on an actually public-reachable server with its own domain. Since nginx also implements a mail server (which you'll need because of domain registration shenenigans) that's something I should look at. Besides that, it'll be development of the wiki theme and dealing with the forum and page ratings.
The latter is actually pretty straightforward now, becaus by virtue of being a lazy bum it seems like the RatePage extension has been developed to include basically every feature we would have needed in the meantime.
Forum… eh. There are plenty interesting things you can do with talk pages, but I'm not much of a fan, tbh. We could juts use redirect magic and use forum software on a different subdomain, but that opens up the question of user accounts. So far I think that's actually the biggest issue we'll be having.
The last thing will be bot protection. And look, I am 100% on board with handing everyone who asks a full wikidump. Period. But we also know that the scraperpocalypse is currently in full swing and you'll be flooded by arseholes trying to train their plagiarism machines on your free content the moment you go live. No idea how to handle that. We can't afford a honeypot, IP-banning doesn't work, Anubis is vibe-coded and JS-dependent, so is Gandalf (I also think Gandalf isn't open source) and CloudFlare is a no.
Oh hey looks like the guy who singelhandedly did more for the modern web than all of GAFAM combined has no clue either. Fuck.
Eschew elucidation, espouse obfuscation.