Replies: 1 comment 3 replies
-
Hi @zoomphoto , You have interpreted it very well, the images are only processed the first time they are "requested" , after that they are stored to the Laravel cache that uses the cache as provided in the cache config. So served later from that cache. I will put some more attention into that use case , I understand what you mean. I don't know if there is a s3 cache driver available in the community but I will search for it. If we have that available then we can store our cached images on s3 too. Thx for this nice thought Have a nice day ☀️ |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hey there, first, thank you for this awesome package! I have a question, as it pertains to the caching of images. Are they just a local cache for that browser?
I am envisioning, that once an image is rendered and pulled, I can save that render to S3, then pull it from S3 at anytime in the future. This way, the first person to view the page gets the loading time, everyone else can pull from cache.
Is that how it does work, or can? I can't see anything in the docs.
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions