Dogpile Elasticache
Dogpile backend for AWS Elasticache Memcache service. Uses pymemcache to connect to nodes of the Elasticache cluster with auto-discovery.
Usage
Install with pip:
$ pip install dogpile_elasticache
Configure a region to use dogpile_elasticache:
from dogpile.cache import make_region
region = make_region().configure(
'elasticache_pymemcache',
arguments = {
'configuration.host': 'XX.XX.cfg.use1.cache.amazonaws.com',
'configuration.port': '11211',
}
)
Development
Install environment:
$ pip install -e .[test]
Run tests (with Nose):
$ nosetests
Release (with zest.releaser):
$ fullrelease
Thanks
Thanks to https://github.com/gusdan/django-elasticache for the cluster discovery code.
Changelog
0.1 (2016-04-11)
Released on Github
Metadata
Release files for dogpile-elasticache 0.1
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 | Actions |
|---|---|---|---|---|
| dogpile_elasticache-0.1.tar.gz | 5.6 kB | Without provenance | Details for dogpile_elasticache-0.1.tar.gz |
Release files / dogpile_elasticache-0.1.tar.gz
| Download URL | dogpile_elasticache-0.1.tar.gz |
|---|---|
| Size | 5.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6ca30e6e3c564bd71ac4a6715a369ffc741eca9ce4fc0204468e66f83ce863fa
|
|
BLAKE2b-256 checksum How to use checksums |
966c84f6ae4ff7fc9c489e87ed9fb770fba852e215e5858f6ad9ebdd0c03a52b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for dogpile-elasticache 0.1
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.