Change Details

It seems to be non-trivial to setup CirrusSearch locally manually in a way where we have a setup similar to production. Lets find out how that would be using vagrant. So setup vagrant, checkout the current patches from {T274903} and try with some test data. Investigation success criteria: [] Patch "[[ https://gerrit.wikimedia.org/r/c/mediawiki/extensions/VisualEditor/+/692930 | Show redirects as part of description in template search ]]" successfully finds `redirecttitle` in api responses from the cirrussearch extension. [] Can be run locally //or// on the test instance. Even better, both. Follow-up * If successful, * Install on the test instance. * Port as a new docker-dev module.

It seems to be non-trivial to setup CirrusSearch locally manually in a way where we have a setup similar to production. Lets find out how that would be using vagrant. So setup vagrant, checkout the current patches from {T274903} and try with some test data. Investigation success criteria: [] Patch "[[ https://gerrit.wikimedia.org/r/c/mediawiki/extensions/VisualEditor/+/692930 | Show redirects as part of description in template search ]]" successfully finds `redirecttitle` in api responses from the cirrussearch extension. [] Can be run locally //or// on the test instance. Even better, both. Follow-up * If successful, * Install on the test instance. * Port as a new docker-dev module. * If unsuccessful, * Ask #discovery-search team for guidance.

It seems to be non-trivial to setup CirrusSearch locally manually in a way where we have a setup similar to production. Lets find out how that would be using vagrant. So setup vagrant, checkout the current patches from {T274903} and try with some test data. Investigation success criteria: [] Patch "[[ https://gerrit.wikimedia.org/r/c/mediawiki/extensions/VisualEditor/+/692930 | Show redirects as part of description in template search ]]" successfully finds `redirecttitle` in api responses from the cirrussearch extension. [] Can be run locally //or// on the test instance. Even better, both. Follow-up * If successful, * Install on the test instance. * Port as a new docker-dev module. * If unsuccessful, * Ask #discovery-search team for guidance.