New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cache images? #3
Comments
Yes. Set a cache rule on your server. |
Could you give an example please? |
If your using something like next.js and next/image, there is some cache settings to be set there: https://nextjs.org/docs/api-reference/next/image#caching-behavior |
do i understand this right, the caching is happening on the client side for the front end? If that's the case, seems a bit odd, that it's not being cached at backend.. |
Oh sorry, mixed together this issue with a next/image thread I'm getting a lot of updates on. Edited. |
But I would recommending using a cache layer in front of this plugin. Wouldn't not expect that's in the scope of this plugin, it has just a single purpose, to generate an images based on the parameters I send to it. See it like a microservice. Cause caching all depends on the rest of the setup in your project. If your using something like Gatsby or Next.js, it will be build into the framework. |
The generated image is not saved in the filesystem, am I right? Thanks |
You can now set About server side caching, for now images are not stored anywhere. |
please extend serverside caching of images |
+1 is this something planned in the future? |
Any progress on this? I really want this to become a reality) how can I help? |
I do not have too much time to work on this at now, sorry! |
Hello there! The feature is done in Also, the new documentation is online! Feedback is welcome! |
How do you manage when you change the image? because the reiszed images are cached and not change. How can i flush that specific image cache? |
Is there a way once requested the image is being cached forever? I don't want to regenerate the image on each call.
The text was updated successfully, but these errors were encountered: