Cloudways for a while had a managed MediaWiki VM offering, but they discontinued that I think. Are there standard best practices for hosting MediaWiki these days, or is that part of your secret sauce...?
Cloudways for a while had a managed MediaWiki VM offering, but they discontinued that I think. Are there standard best practices for hosting MediaWiki these days, or is that part of your secret sauce...?
Generally I would go with Canasta, a Docker image that's collectively maintained by a few MediaWiki companies. Canasta upgrades with every LTS release, which is a much easier pace for maintainers. https://github.com/CanastaWiki/Canasta
Parsoid got ported to PHP and made a core feature in 2019 and no longer requires being run as a separate Node.js service. The Visual Editor (which most people ran Parsoid to get) just works out of the box now.
Update difficulty scales about evenly with the number of third-party extensions you rely on, especially if CirrusSearch or Semantic MediaWiki are among them. But if you stick to stock and to the LTS version line, it's relatively painless since 1.19 compared to before it.
Between general PHP performance improvements and php-fpm compatibility, it's frankly overkill to run anything beyond the official mediawiki:lts-fpm Docker image[1] while applying whatever PHP config changes you need for your use cases to the Dockerfile. Throw in SQLite improvements and even bare-metal admin isn't much of a hassle these days compared to the bad old days of juggling PHP versions and extensions, configuring Varnish, running Parsoid, patching Mediawiki extensions and skins, and doing MySQL/MariaDB/Postgres upgrades.
A handful of well-supported responsive Mediawiki skins also means the stupid mobile-domain tricks aren't necessary anymore for most users to have a decent experience.
I'll have to check back in with that wiki I used to help with and see what they're doing these days...
Cargo's still easier to work with and its query syntax is a lot more SQL-like, even with the reduced feature set.