Holy cow I think that's exactly what the problem is. I will give that a try and let you know what happens!
On Tue, Apr 3, 2018 at 10:50 AM, Mark Sapiro <mark@msapiro.net> wrote:
Hello,
If I'm reading the docs correctly, when we run manage.py update_index, it should be an incremental index of new emails that have been added since
On 04/03/2018 09:02 AM, Darren Smith wrote: the
last time update_index was run - can anyone confirm that this is the expected behavior? Or is there another command line option that I am missing?
There are two ways to run update_index.
Hyperkitty's update_index is incremental and is run by
manage.py runjob update_index
Running
manage.py update_index
runs haystack's update_index which with no options does a full update. Run
manage.py update_index --help
to see the options. The incremental 'manage.py runjob update_index' should be run every minute by 'manage.py runjobs minutely' assuming cron is running the periodic Django jobs, so running either update_index job manually shouldn't be necessary
...
So...can anyone help with how to get the update_index to do only emails added since the last time the update_index was run?
manage.py runjob update_index
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-users mailing list mailman-users@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/