Closed thisisaaronland closed 8 years ago
Assigning to you (@dphiffer) since it sounds like you got to this first. Can you add notes explaining what the what is?
Sure thing. The idea is that sometimes an action that has a simple interface (i.e., "update these 20 records") has quite a few sub-tasks, some of which may take longer to complete than the user wants to wait around for.
I just committed the first set of updates that takes care of the task handoff to Gearman. That in turn gets executed by worker code that runs in the background.
The next time we update the Sky Box, we'll need to make sure there are Gearman workers running, so that those incoming tasks don't fall on deaf ears. That's the part I am working on next.
Some additional thoughts on more system-level Gearmand stuff, one week later:
services
folder/etc/supervisor/conf.d
Yes to the supervisor.d
stuff and no to the gearman_worker.php
stuff for two reasons:
bin
directory already introduces an annoying level of complexity (see bin/init_local.php
) and I don't want to add any other rules, conditions, exceptions.Cool, I'll leave the worker in bin.
See also: issue #58