Last modified: 2014-02-08 07:57:40 UTC
Splitting the rift-raft out of closely related bug 25682. Please document the process of setting up the search indexers for new projects on wikitech.
Unassigning default assignments. http://article.gmane.org/gmane.science.linguistics.wikipedia.technical/54734
Documentation can be found here: http://www.mediawiki.org/wiki/Extension:Lucene-search/2.0_docs
Reopening. Searching is still broken in newly created projects, for example: * http://lez.wikipedia.org * http://vep.wikipedia.org There are probably more. The procedure for creating a new project must be more robust, so this won't happen. Enabling proper and usable searching is not something that can be forgotten.
http://wikitech.wikimedia.org/view/Search#Adding_new_wikis
The idea is not just to document how it is done, but to document it in such a way that it's not forgotten again. At the very least it must be mentioned here: http://wikitech.wikimedia.org/view/Add_a_wiki
[Merging "MediaWiki extensions/Lucene Search" into "Wikimedia/lucene-search2", see bug 46542. You can filter bugmail for: search-component-merge-20130326 ]
Repurposing for CirrusSearch, we need to expand the documentation. https://wikitech.wikimedia.org/wiki/Search/New
I've made some significant updates to the documentation at https://wikitech.wikimedia.org/wiki/Search/New so I'm assigning this to Andrew Otto for review.
Cool! - https://wikitech.wikimedia.org/wiki/Search/New#Current_setup is no longer correct - https://wikitech.wikimedia.org/wiki/Search/New#Administration is it true that arsenic is still the correct place to run indexing scripts? - One thing I like to do when writing shell command documentation, is use an actual $placeholder variable name in instead of <placeholder>. That way someone can do wikiname=wikidata And copy/paste your commands in exactly. Nik, this looks really great. The next time you have a task to complete that is documented here, you should see if you can get me to do it with help mostly (if not only) from the documentation. That'll help us find any missing parts. BTW, your documentation thoroughness is inspiring! I shall aspire to match yours with the analytics documentation soon!
(In reply to comment #9) > Cool! > > - https://wikitech.wikimedia.org/wiki/Search/New#Current_setup is no longer > correct Done. > > - https://wikitech.wikimedia.org/wiki/Search/New#Administration is it true > that > arsenic is still the correct place to run indexing scripts? Nope it is broken and using it will only lead to sorrow. Fixed. > - One thing I like to do when writing shell command documentation, is use an > actual $placeholder variable name in instead of <placeholder>. That way > someone can do > > wikiname=wikidata > > And copy/paste your commands in exactly. Done. > Nik, this looks really great. The next time you have a task to complete that > is documented here, you should see if you can get me to do it with help > mostly > (if not only) from the documentation. That'll help us find any missing > parts. I have a deployment today but I want to do it myself for my own comfort level. > BTW, your documentation thoroughness is inspiring! I shall aspire to match > yours with the analytics documentation soon! Nice! It helps that search is all I work on.
I'm closing this because the Cirrus documentation is pretty extensive now. If it needs something just poke me or Chad and we'll do it.
