cachefly – convenient CacheFly CDN management
The CacheFly CDN exposes an HTTP based API for forcefully purging content from their reverse proxying CDN solution. The cachefly module provides a simple interface for performing those actions.
Furthermore, the django_cachefly module provides a convient way to configure and access an application wide API client instance through your Django settings.
Installation
To install cachefly and django_cachefly, do yourself a favor and don’t use anything other than pip:
$ pip install cacheflyInstallation in Django
After the module has been installed, you need to add django_cachefly to your list of INSTALLED_APPS in your application configuration:
INSTALLED_APPS = (
...
'django_cachefly',
)You also need to configure your CacheFly API key in your application’s settings file:
CACHEFLY_API_KEY = '..'The CacheFly API client can now be easily accessed from the entire application:
from django_cachefly import client
...Testing
Testing requires a set of valid credentials. All tests are performed against URLs in the /_testing path for the CDN node your select. Credentials are loaded from the environment during testing for security:
- CACHEFLY_API_KEY
API key to use for testing.
1 maintainer
Metadata
1 maintainer
Release files for cachefly 1.0.0
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 | |
|---|---|---|---|---|
| cachefly-1.0.0.tar.gz | 3.3 kB | Without provenance | Details |
Release files / cachefly-1.0.0.tar.gz
| Download URL | cachefly-1.0.0.tar.gz |
|---|---|
| Size | 3.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2dc700bd0f344958dfbbfcffb2ca669e41a587d27ece7e3e82ee09edd6a2d11b
|
|
BLAKE2b-256 checksum How to use checksums |
cb1906da7e862a09195ea8b72a90bb8cad2d131e536512923a4494f6217e311e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for cachefly 1.0.0
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.
