Image service
Library to create image proxying services.
The most basic usecase is serving images through HTTPS and stripping information from the original request, similar to what [camo](https://github.com/atmos/camo) does.
Imgservice brings it a step forward by allowing:
Non-http(s) sources (eg. private S3 buckets, …)
Image processing (resizing, cropping, …)
URL format and security
URLs are in the format: https://example.com/<token>, where token is a (signed, b64 encoded) object describing the image source and any required transformations.
Configuration
All the configuration is done by writing a simple Python script that imports and makes use of the imgservice library.
Testing
To run the test suite:
docker-compose run –rm -e PYTHONHASHSEED=0 web py.test -vvv –cov=imgservice –cov-report=term-missing ./tests
1 maintainer
Metadata
1 maintainer
Release files for Imgservice 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 |
|---|---|---|---|---|
| Imgservice-0.1.tar.gz | 7.4 kB | Without provenance | Details for Imgservice-0.1.tar.gz |
Release files / Imgservice-0.1.tar.gz
| Download URL | Imgservice-0.1.tar.gz |
|---|---|
| Size | 7.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cd73db99129ae9e00f56b28957c52e5622a33cf4e8bd1adc91268f7b4ad26479
|
|
BLAKE2b-256 checksum How to use checksums |
dcae877b1d0cc46c0d508ebd0c8d17f1a191bd30b67f10c912542f2bb02e2f96
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for Imgservice 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.
