ImageMagick requirement about vue-storefront-api HOT 8 CLOSED

I will take care of this.

On a second note, I am trying to rewrite src/api/img.js to use libvips , which is 5x faster (according to their docs) than imageMagik and does not have any system dependencies. Also looking at better image cache instead of using /tmp. Something that supports configurable invalidation and multiple engines. I considered ES as img storage for a while but until ES 6.4, blob storage type is not really worth it.

I am taking my time on this one as I do not have that much time but I think relying on a lib (imagable) that no longer exists (github 404) is a wrong move to begin with.

from vue-storefront-api.

should there not be a fallback for other image libraries, or serve the image not resized if no image libraries are found ?

from vue-storefront-api.

Another solution would be to server the api on a docker instance and set the requirements ourselves,
install the dependencies as needed, which also reduces the access to ES to have a public port mapped

from vue-storefront-api.

You're right. Could you please take care of this (I mean - updating the docs that Imagemagick is required + maybe some warning message in the vue-storefront-api console?)

The fallback would probably require quite a lot of work - so I belive the warning + docs is enough

WDYT @DarkMukke ?

from vue-storefront-api.

Cool, fingers crossed for this!

from vue-storefront-api.

https://github.com/lovell/sharp looks like a good candidate:

• It replaces ImageMagick with https://github.com/jcupitt/libvips which seems faster
• It's a node lib, so we can ditch our current wrapper for ImageMagick (less code)

from vue-storefront-api.

Related to:
vuestorefront/vue-storefront#165

@DavidRouyer Would be great if You can take care of this

from vue-storefront-api.

See #110

from vue-storefront-api.