Skip to content
This repository has been archived by the owner on May 28, 2023. It is now read-only.

Implemented basic image processing/caching factories #315

Conversation

ResuBaka
Copy link
Collaborator

With this we get a local action witch is the current behavior.
Then we have file caching which is disabled by default. This creates
and md5 of the URL and for that he saves the processed image to file.

With this you can change the logic of caching (s3, redis, ...) and you can change the implementation of processor which and what you can to with the image.

This is a basic implementation and I would think needs better naming.

With this we get a local action witch is the current behavior.
Then we have file caching which is disabled by default. This creates
and md5 of the URL and for that he saves the processed image to file.
@ResuBaka
Copy link
Collaborator Author

One thing that is missing is a google cloud storage implementation for caching which I now going to work on.

Copy link
Contributor

@pkarw pkarw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is so awesome!

@pkarw pkarw merged commit 589bb87 into vuestorefront:develop Jul 24, 2019
ResuBaka added a commit to gastrohero/vue-storefront-api that referenced this pull request Jul 26, 2019
@nitin-bc
Copy link

nitin-bc commented Feb 2, 2020

Hi, @ResuBaka Does it work for other media images as well apart from product and category? I mean for static blocks or CMS pages?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants