Pilbox is an image resizing application server built on Python's Tornado web framework using the Python Imaging Library (Pillow). It is not intended to be the primary source of images, but instead acts as a proxy which requests images and resizes them as desired.
- Pillow 2.1.0
- Tornado 3.1
- OpenCV 2.x
- Image Libraries: libjpeg-dev, libfreetype6-dev, libwebp-dev, zlib1g-dev
Packaged with Pilbox is a Vagrant configuration file which installs all necessary dependencies on a virtual box. See the Vagrant documentation for installation instructions. Once installed, the following will start a virtual machine.
$ vagrant up
To access the virtual machine itself, simply...
$ vagrant ssh
To run the application, issue the following command
$ python -m pilbox.app
By default, this will run the application on port 8888 and can be accessed by visiting:
To see a list of all available options, run
$ python -m pilbox.app --help Usage: pilbox/app.py [OPTIONS] Options: --allowed_hosts list of allowed hosts (default ) --background default hexadecimal bg color (RGB or ARGB) --client_key client key --client_name client name --config path to configuration file --debug run in debug mode (default False) --filter default filter to use when resizing --help show this help information --max_requests max concurrent requests (default 40) --port run on the given port (default 8888) --position default cropping position --quality default jpeg quality, 0-100 --timeout timeout of requests in seconds (default 10)
When running via Vagrant, the application is automatically started on port 8888 on 192.168.100.100, i.e.
To use the image resizing service, include the application url as you would any other image. E.g. this image url
<img src="http://i.imgur.com/zZ8XmBA.jpg" />
Would be replaced with this image url
<img src="http://localhost:8888/?url=http%3A%2F%2Fi.imgur.com%2FzZ8XmBA.jpg&w=300&h=300&mode=crop" />
This will request the image served at the supplied url and resize it to
300x300 using the
crop mode. The following is the list of parameters that can be supplied to the service
- url: The url of the image to be resized
- _w_: The desired width of the image
- _h_: The desired height of the image
- mode: The resizing method: clip, crop (default), fill and scale
- clip: Resize to fit within the desired region, keeping aspect ratio
- crop: Resize so one dimension fits within region, center, cut remaining
- fill: Fills the clipped space with a background color
- scale: Resize to fit within the desired region, ignoring aspect ratio
- filter: The filtering algorithm used for resizing
- nearest: Fastest, but often images appear pixelated
- bilinear: Faster, can produce acceptable results
- bicubic: Fast, can produce acceptable results
- antialias: Slower, produces the best results
- fmt: The output format to save as, defaults to the source format
- jpeg: Save as JPEG
- png: Save as PNG
- webp: Save as WebP
- _bg_: Background color used with fill mode (RGB or ARGB)
- RGB: 3- or 6-digit hexadecimal number
- ARGB: 4- or 8-digit hexadecimal number, only relevant for PNG images
- pos: The crop position
- top-left: Crop from the top left
- top: Crop from the top center
- top-right: Crop from the top right
- left: Crop from the center left
- center: Crop from the center
- right: Crop from the center right
- bottom-left: Crop from the bottom left
- bottom: Crop from the bottom center
- bottom-right: Crop from the bottom right
- face: Identify faces and crop from the midpoint of their position(s)
- _q_: The quality (1-100) used to save the image, only relevant to JPEGs.
- client: The client name
- sig: The signature
url, and either
h parameters are required. If only one dimension is specified, the application will determine the other dimension using the aspect ratio.
mode is optional and defaults to
filter is optional and defaults to
fmt is optional and defaults to the source image format.
bg is optional and defaults to
pos is optional and defaults to
q is optional and defaults to
client is required only if the
client_name is defined within the configuration file. Likewise,
sig is required only if the
client_key is defined within the configuration file. See the signing section for details on how to generate the signature. Note, all built-in defaults can be overridden by setting them in the configuration file. See the configuration section for more details.
The following images show the various resizing modes in action for an original image size of
640x428 that is being resized to
The image is resized to fit within a
500x400 box, maintaing aspect ratio and producing an image that is
500x334. Clipping is useful when no portion of the image can be lost and it is acceptable that the image not be exactly the supplied dimensions, but merely fit within the dimensions.
The image is resized so that one dimension fits within the
500x400 box. It is then centered and the excess is cut from the image. Cropping is useful when the position of the subject is known and the image must be exactly the supplied size.
Similar to clip, fill resizes the image to fit within a
500x400 box. Once clipped, the image is centered within the box and all left over space is filled with the supplied background color. Filling is useful when no portion of the image can be lost and it must be exactly the supplied size.
The image is clipped to fit within the
500x400 box and then stretched to fill the excess space. Scaling is often not useful in production environments as it generally produces poor quality images. This mode is largely included for completeness.
To run all tests, issue the following command
$ python -m pilbox.test.runtests
To run individual tests, simply indicate the test to be run, e.g.
$ python -m pilbox.test.runtests pilbox.test.signature_test
In order to secure requests so that unknown third parties cannot easily use the resize service, the application can require that requests provide a signature. To enable this feature, set the
client_key option. The signature is a hexadecimal digest generated from the client key and the query string using the HMAC-SHA1 message authentication code (MAC) algorithm. The below python code provides an example implementation.
import hashlib import hmac def derive_signature(key, qs): m = hmac.new(key, None, hashlib.sha1) m.update(qs) return m.hexdigest()
The signature is passed to the application by appending the
sig paramater to the query string; e.g.
x=1&y=2&z=3&sig=c9516346abf62876b6345817dba2f9a0c797ef26. Note, the application does not include the leading question mark when verifying the supplied signature. To verify your signature implementation, see the
pilbox.signature command described in the tools section.
All options that can be supplied to the application via the command line, can also be specified in the configuration file. Configuration files are simply python files that define the options as variables. The below is an example configuration.
# General settings port = 8888 # Set client name and key if the application requires signed requests. The # client must sign the request using the client_key, see README for # instructions. client_name = "sample" client_key = "3NdajqH8mBLokepU4I2Bh6KK84GUf1lzjnuTdskY" # Set the allowed hosts as an alternative to signed requests. Only those # images which are served from the following hosts will be requested. allowed_hosts = ["localhost"] # Request-related settings max_requests = 50 timeout = 7.5 # Set default resizing options background = "ccc" filter = "bilinear" format = None mode = "crop" position = "top" quality = 90
To verify that your client application is generating correct signatures, use the signature command.
$ python -m pilbox.signature --key=abcdef "x=1&y=2&z=3" Query String: x=1&y=2&z=3 Signature: c9516346abf62876b6345817dba2f9a0c797ef26 Signed Query String: x=1&y=2&z=3&sig=c9516346abf62876b6345817dba2f9a0c797ef26
The application allows the use of the resize functionality via the command line.
$ python -m pilbox.image --width=300 --height=300 http://i.imgur.com/zZ8XmBA.jpg > /tmp/foo.jpg
If a new mode is added or a modification was made to the libraries that would change the current expected output for tests, run the generate test command to regenerate the expected output for the test cases.
$ python -m pilbox.test.genexpected
The application itself does not include any caching. It is recommended that the application run behind a CDN for larger applications or behind varnish for smaller ones.
Defaults for the application have been optimized for quality rather than performance. If you wish to get higher performance out of the application, it is recommended you use a less computationally expensive filtering algorithm and a lower JPEG quality. For example, add the following to the configuration.
# Set default resizing options filter = "bicubic" quality = 75
- 0.1: Image resizing fit
- 0.1.1: Image cropping
- 0.1.2: Image scaling
- 0.2: Configuration integration
- 0.3: Signature generation
- 0.3.1: Signature command-line tool
- 0.4: Image resize command-line tool
- 0.5: Facial recognition cropping
- 0.6: Fill resizing mode
- 0.7: Resize using crop position
- 0.7.1: Resize using a single dimension, maintaining aspect ratio
- 0.7.2: Added filter and quality options
- 0.7.3: Support python 3
- 0.7.4: Fixed cli for image generation
- 0.7.5: Write output in 16K blocks
- 0.8: Added support for ARGB (alpha-channel)
- 0.8.1: Increased max clients and write block sizes
- 0.8.2: Added configuration for max clients and timeout
- 0.8.3: Only allow http and https protocols
- 0.8.4: Added support for WebP
- 0.8.5: Added format option and configuration overrides for mode and format
- How to reconcile unavailable color profiles?
- Add backends (S3, file system, etc...) if necessary
- test commit