Mailman 3 Hyperkitty indexes not being built
My config looks like this:
HAYSTACK_CONNECTIONS = { 'default': { 'ENGINE': 'haystack.backends.whoosh_backend.WhooshEngine', 'PATH': os.path.join(BASE_DIR, "fulltext_index"), ... I have whoosh 2.7.4 installed. But my fulltext_index directory contains only one file, _MAIN_0.toc, which hasn't been updated in two years.
What could be going on here? Presumably Hyperkitty should be indexing new messages as they are archived. I could run update_index to fix the index now but then it would just go out of date again.
Also asked on SO: https://stackoverflow.com/questions/74055901/mailman-3-hyperkitty-indexes-no...
Thank you!
On 10/18/22 05:27, tom@gather.coop wrote:
My config looks like this:
HAYSTACK_CONNECTIONS = { 'default': { 'ENGINE': 'haystack.backends.whoosh_backend.WhooshEngine', 'PATH': os.path.join(BASE_DIR, "fulltext_index"), ... I have whoosh 2.7.4 installed. But my fulltext_index directory contains only one file, _MAIN_0.toc, which hasn't been updated in two years.
What could be going on here? Presumably Hyperkitty should be indexing new messages as they are archived. I could run update_index to fix the index now but then it would just go out of date again.
Also asked on SO: https://stackoverflow.com/questions/74055901/mailman-3-hyperkitty-indexes-no...
And answered there. You need to be running several things periodically via cron. For Mailman core, see https://docs.mailman3.org/en/latest/config-core.html#configuring-cron-jobs and for Django, see https://docs.mailman3.org/en/latest/config-web.html#scheduled-tasks-required.
The particular job which updates the search index is the hyperkitty update_index job which in current HyperKitty is one of the hourly jobs.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Mark Sapiro
-
tom@gather.coop