shifr/imgwizard

Simple server for On-the-Fly image processing in Go

imgwizard's Issues

Deploying to aws lambda

Would it be possible? Serverless solution is far more reliable and cheap than servers in this case

Cropping by sides

Add GET parameters "?crop=side1,side2". Now images are cropped by center

Single axis scaling works inconsistently across axes

e.g.

• https://m3.cdnmk.net/imgw/loc/100x/uploads/product_image/2016/07/005/ae021b15-858b-4b66-af0c-b23528dc414e_67605c9b13ae4fe34b3bf08685405c3a_1x1.jpg (locked width, free height) scales to fit, as expected, ie. returns a 100x139 image.
• https://m3.cdnmk.net/imgw/loc/x100/uploads/product_image/2016/07/005/ae021b15-858b-4b66-af0c-b23528dc414e_67605c9b13ae4fe34b3bf08685405c3a_1x1.jpg (locked height, free width) returns a 100x100 image, scaled to fill. That kinda defeats the purpose, if I'd wanted both of the axes locked, I'd request exactly that in the first place.

Stats page

add statistic page to get performance stats:
current active/waiting request,
received/accepted/processed requests from daemon start

Add ability to notify each process about others

Something like this:
imgw1, imgw2, imgw3, imgw4
imgw1 knows about imgw2, imgw3, imgw4
imgw2 knows about imgw1, imgw3, imgw4 etc.

Therefore we can cache one file one time at one node and request each node before process resize. It prevents overcaching

Limit resize size by size of original

It's possible to send request with size bigger than original. Much more bigger:
ll 133/fc3cb123-cf43-45d3-822f-472aa84f5389_546e81b73d4fbe9472b041afd9723227_1x1_41400x57600.jpeg -h
-rw-r--r-- 1 www www 46M Oct 17 13:27 fc3cb123-cf43-45d3-822f-472aa84f5389_546e81b73d4fbe9472b041afd9723227_1x1_41400x57600.jpeg

You can easily use this to overflow cache partition.
Wise solution will be - return original size if requested sizemore than original

Return 404 status when image not found

Support image/pjpeg

Progressive JPEG has numerous advantages over other image formats when used over poor connection/on mobile.

When resulting image is heavier than a source, then a source one should be used

Ability to disable/enable webp conversion

HEAD request returns 404

> curl -I https://media.modnakasta.ua/imgw/loc/460x280/uploads/campaign/2015/07/050/d3d93a5a-ae5b-4240-b2af-c7db0c16635a_ac5201fe3f0e21da034828d97a07de3c.jpg                                                            
HTTP/1.1 404 Not Found
Server: nginx
Date: Mon, 06 Jul 2015 09:07:58 GMT
Content-Type: text/plain; charset=utf-8
Content-Length: 19
Connection: keep-alive

Use sendfile in cache

Add ability to silence all logs

Add media white list

Add config for remote media white list to prevent use your imgwizard by others

"no cache" option

add URL path to prevent request cache

Make it possible to limit the range of possible image sizes

Subj. Your /tmp will die if I want to make 100000 size variants of the site's images. Something like:

RESIZE_PARAMS_RANGE = 100x50, 420x, 800x

And disable any processing if my resize param is out of this range. Should be great.