Extension:GrowthExperiments/developer setup


 * See MediaWiki-Docker/Extension/GrowthExperiments for the Docker setup, and the  role for the Vagrant setup.

There are three basic approaches for setting up suggested edits, the main functionality of GrowthExperiments, in a developer setup:
 * 1) Have the extension use the search API of a remote (production) wiki. You won't have to deal with setting up search locally, and you will get a wide range of realistic task suggestions, but the articles suggested for those tasks won't exist on your wiki so most editing-related functionality won't work. This is the easiest way to get the homepage and guidance working in general, and to QA task suggestions. It doesn't work for structured link recommendations though since those aren't enabled on any production wiki yet.
 * 2) Set up search locally, copy-paste or import a couple articles from some real wiki. This is quite a bit more effort but doable (on Vagrant it should mostly work out of the box). It's good for backend development, probably not really worth the effort for frontend development.
 * 3) Mock all the backend logic involved with static PHP code. This is nice for frontend work as you get direct and full control over the responses from the backend.

Set up search locally
Refer to the setup notes of Extension:CirrusSearch. You can use the CirrusSearch maintenance script  for setting the ORES topics of wiki pages.