A repository that wraps the provided Bungiesearch signal processing class in your own celery tasks.
This Django app allows you to utilize Celery for automatically updating and deleting objects in a Bungiesearch search index.
Compatible with most recent version of Bungiesearch, which is similar to Haystack, but interacts directly with elasticsearch-dsl and therefore allows for more custom ranking functions.
Install
pip install celery-bungiesearch
Requirements
Django 1.4.3+
Bungiesearch 1.2.1+
Celery 3.1.18+
Usage
1. Add 'celery_bungiesearch' to INSTALLED_APPS in settings
INSTALLED_APPS = [
# ..
'celery_bungiesearch',
]
2. Add CelerySignalProcessor to settings.BUNGIESEARCH['SIGNAL_CLASS'] in settings. This will ensure that any model that’s managed by a BungiesearchManager acquire CelerySignalProcessor as the signal processor.
from celery_bungiesearch import CelerySignalProcessor
BUNGIESEARCH = {
# ..
'SIGNALS': {
'SIGNAL_CLASS': 'celery_bungiesearch.signals.CelerySignalProcessor',
'BUFFER_SIZE' : 100
}
}
3. Add celery-bungisearch configuration variables to your settings file. The task below is the default version, but you may include your own custom classes if you desire (note that none of these environment variable are required, and can be entirely excluded from the settings file):
CELERY_BUNGIESEARCH_QUEUE = None
CELERY_BUNGIESEARCH_TASK = 'Your custom index task path'
CELERY_BUNGIESEARCH_CUSTOM_TASK = 'Your custom celery task path'
4. Ensure your Celery instance is running.
Testing
You can run tests locally for celery-bungiesearch by simply running the command tox or tox test. You must have an instance of elasticsearch running locally. You can also run tests using continuous integration with Travis CI (build status at the top of this README).
Thanks
This application borrows liberally from Jannis Leidel’s celery-haystack and from Christopher Rabotin’s Bungiesearch, which itself was the inspiration for this project.
Issues
Please submit a pull request or use the Github issue tracker for any bug fixes, bug reports, or feature requests.
Metadata
Release files for celery-bungiesearch 1.2.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| celery-bungiesearch-1.2.4.tar.gz | 6.4 kB | Without provenance | Details |
Release files / celery-bungiesearch-1.2.4.tar.gz
| Download URL | celery-bungiesearch-1.2.4.tar.gz |
|---|---|
| Size | 6.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8ea45450066b9bdee2c4821b00d8888d71f41d94cfd1daeccc30a58b72b0103a
|
|
BLAKE2b-256 checksum How to use checksums |
15c8d7157c9e5560fc250ec0a5166548f6f70b4e3f466ea53b9327d7210c86c5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for celery-bungiesearch 1.2.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.