Disable image preset generation on upload?

[klickreflex]

Statamic always generates all image presets defined in assets.image_manipulation.presets on upload.
This is nice if all your images are required in any preset available, but it can quickly blow up disk space when dealing with lots of images in many different formats, where. not every image is required in every format/preset.

I usually have a bunch of image presets that are used in some components, but many other components have custom glide settings and are only ever displayed in this variant.

Another scenario might be using preset 1 only in component A, and preset 2 only in component B. So preset 1 is never needed for an image used in component B and preset 2 is never needed for an image used in component A, yet all defined variants are generated and stored on disk forever (or until please glide:clear is run).

It would be cool if we could just disable the automatic generation of presets upon upload with a config option. (SAVE_CACHED_IMAGES has no effect on this behavior).

[Alpenverein]

Would be interesting for me too. We had a first test of our new system with a bigger group of our future editors. When they started to write articles and uploaded images, the system became slower and slower and finally stopped working/responding. I found out, that the reason was the calculation of all the different image presets....

So: Yes please!

[jesseleite]

@klickreflex @Alpenverein This is already implemented in statamic/cms#6040, where you'll be able to glide_warm_presets: false to completely disable, or specify which image manipulation presets each container pre-warms on upload. Not merged yet, but probably coming soon! 👍

[klickreflex]

@jesseleite This is great news, thanks 🙏
Once merged, where would I set glide_warm_presets: false? I can't find any new config in statamic/cms#6040

[jesseleite]

@klickreflex It would go on your asset container yaml file. There'll also be control panel UI for this in the asset container's settings...

[klickreflex]

Oh nice, thanks for explaining @jesseleite