Setting up MediaWiki properly yourself is not a small undertaking. How wikipedia does what they do is with puppet deployments and a significant amount of automa

Setting up MediaWiki properly yourself is not a small undertaking. How wikipedia does what they do is with puppet deployments and a significant amount of automatic server management. It's incredibly inefficient given that pages should be statically served, it's very difficult to even know what to install and it may not even be future compatible. For example getting VisualEditor, MediaWiki's custom PHP-lua extension for your version of PHP, needing PHP-FPM, managing versions of PHP, correct configs. Setting up page caching, knowing what extensions to get, seeing lots of out of date ones, having to configure them properly. Ontop of all this doing it actually right with proper file and user permissions is just completely inaccessible to anyone but those who make a job of it. Even the mediawiki 'package' is out of date and works differntly, causing more problems. It should be as simple as getting a domain, getting cloudflare, pop up a $5 VPS and a couple commands to have a proper and automatically updated install. User sets up website, sets backups to GDrive or some other cloud service, allows logins from google, facebook, whatever, and can then manage everything from the UI.