| | 1 | |
| | 2 | = Worker basics = |
| | 3 | |
| | 4 | Background workers are small programs that will consume queue notifications generated by CKAN and act upon those. Examples could include web hooks notifiers, email sending processes, the search engine indexer or archival daemons. |
| | 5 | |
| | 6 | * [http://bitbucket.org/pudo/ckanextworker/src/tip/README.md API and usage docs] |
| | 7 | * [http://bitbucket.org/pudo/ckanextworker Workers repo] |
| | 8 | |
| | 9 | = Known workers = |
| | 10 | |
| | 11 | * "test" worker (included in ckanextworker) |
| | 12 | * [http://bitbucket.org/pudo/ckanextarchive Ckan EXT Archive] - Downloads package data |
| | 13 | |
| | 14 | = Current notes = |
| | 15 | |
| | 16 | * The search indexer in ckanext really should be a worker and needs to be refactored to reflect that |
| | 17 | * Workers are on eu4, ran by the user "worker" - monitored and executed via supervisord. |
| | 18 | * Indexers are on eu4, ~okfn/var/ckanext/ckanext/solrindexer - monitored and executed via supervisord. |
| | 19 | * We need to handle stale data. Assume, for example, that a package notification is first handeled by a "statisticsworker" that would add some data. The next worker (Emailworker) should now receive an updated version of the package. |
