Here’s the handler: https://aws.amazon.com/solutions/serverless-image-handler/
Basically - it does image processing for us, but we don’t want to download any images as we generate that “derivatives”, and we don’t want to upload anything to S3 (and we don’t even care much about metadata really).
So it seems like
derivatives plugin does not really fit in this case. (It would if we wanted to upload that image, and/or cared about the metadata of those processed images.)
What we could do instead:
- generate a URL for a processed image dynamically each time on the Front End, as described here in step 2: https://docs.aws.amazon.com/solutions/latest/serverless-image-handler/deployment.html
And, I guess that’s the best and most flexible way of doing it, so Shrine is not even directly involved in all that serverless image handling at all!
Funny, it was kinda a question when I was about to write it, and in progress of writing I’ve already figured it out. But I’ve already written it, so maybe that’s something that might be added to Shrine documentation somewhere (and also reviewed by someone like Janko first ).