==============
Common and easy way to manage ES backend in django based on elasticutils and
elasticsearch-py.
Hacking
-------
In order to hack on django-esutils, you'll need to set at least an Elasticsearch
instance available from your machine.
You can install it manually or more simply, use a docker container like this::
docker run --net host dockerfile/elasticsearch
and then you can browse your ES server at: http://127.0.0.1:9200/
Configuration
~~~~~~~~~~~~~
add a :file:`local_settings.py` file in your :file:`demo/demo_esutils` directory,
with these settings:
.. code-block:: python
ES_URLS = [
'http://127.0.0.1:9200',
]
(or change it to fit your ES target configuration)
Running tests
~~~~~~~~~~~~~
Now that your ES instance is ready, and your database connection set, simply run
the tests using tox, preferrably in a virtualenv::
mkvirtualenv TOX
pip install tox
tox
Metadata
Release files for django-esutils 0.3
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 | |
|---|---|---|---|---|
| django-esutils-0.3.zip | 12.7 kB | Without provenance | Details |
Release files / django-esutils-0.3.zip
| Download URL | django-esutils-0.3.zip |
|---|---|
| Size | 12.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d9ccda86df0b4a5a85e4e36b6c00de9e691db1cc806529a31deb946c7a212ffb
|
|
BLAKE2b-256 checksum How to use checksums |
c2a51c9ef0dab0e73c49ac8433b80772c0b87d3acce9c3ad1b10671597a1790b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-esutils 0.3
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.