Hi JB,

The main reason of why it's currently unsupported is because I don't have access to S3 buckets, nor do I have experience integrating C5 with S3 (e.g. via an add-on). I expect that building and testing the functionality will at least take two full days, so I'm not too interested in it. I hope you understand!

A3020

I understand where you're coming from. I've been using Mnkras' addon for that (https://www.concrete5.org/marketplace/addons/storage-for-amazon-s3). So perhaps I could suggest that you ask him for a copy to use for development, and if you can make your add-on compatible with that, you both do cross promotion. Anyone who is serious about storing their website files also would be serious about compression (I know I am). So they both go hand in hand.

What do you say?

I agree with you, but business wise it's not worth the effort. I also risk breaking existing functionality, an increase of support tickets, and maybe even technological hindrances. I guess for those running large websites with S3 storages, I'd recommend taking a look at CDN image optimization.

I asked Mnkras about him adding support for your add-on in his Amazon S3 add-on (https://www.concrete5.org/marketplace/addons/storage-for-amazon-s3/support/feature-request-thumbnail-optimisation-integration/) and if I understand correctly he just uses the C5 file system. So if your optimisation is done BEFORE it's uploaded to a remote location then it could work out of the box.

Would I be able to run a test before purchasing?

Hi jb1, thanks for your message. The image optimization doesn't happen right after upload, but periodically (cron / cli) or manually triggered via the Automated Jobs page. I *suspect* that files are sent to S3 during the upload process. Can you confirm that? If so, I don't see how the two add-ons would be compatible out of the box.

Ah yeah, they are deleted off the server after being uploaded. So I guess they're not going to play. My next stop is an Amazon lambda function to do the optimisation.
Thanks anyway.