mozilla/kuma — pull request #923 by groovecoder (2013-03-12 18:25:19+00:00)
Title: Es search view 839214

(Would like to get @lmorchard and/or @ubernostrum to think about [my forcing the override of settings from test-utils](https://github.com/groovecoder/kuma/pull/new/es-search-view-839214#L0R117))

Supersedes #898. The same testing instructions apply, plus some new ones:

You'll need to fetch [my kuma-lib repos](https://github.com/groovecoder/kuma-lib), which means [the leeroy/mdn-github jenkins build](https://ci.mozilla.org/job/mdn-github/) is going to fail.

1. `git submodule update --init --recursive`
2. `vagrant provision`
3. Run tests. Make sure to include the 'search' app.

To spot-check, make sure you're running `./manage.py celeryd`, then:

1. update a doc in the site UI
2. go to https://developer-local.allizom.org/elastic/_plugin/head/
3. connect it to https://developer-local.allizom.org/elastic/
4. go to the 'Browser' tab and make sure there's a record in the `mdn-main_index` for the doc

To spot-check the search view (wiring only, nothing fancy):

1. go to https://developer-local.allizom.org/admin/waffle/flag/
2. add flag 'elasticsearch' active for your user
3. go to https://developer-local.allizom.org/en-US/search

You should see a simple search result list matching the ES index.