Open 3x071c opened 2 years ago
Update: We can use persistent volumes on Fly to store uploaded images. Via a GitHub cronjob, we can then iterate over the uploaded images every day and optimize them via sharp. The <Image>
component then sources the images from the volume mount point and first attempts to load an optimized version for the client before resorting to the original.
Rescheduling to M3
There are multiple components to this, which should be split into their own issues:
Image
component that serves optimized, responsive imagesWe should consider delegating image optimization to a dedicated service, such as imaginary, which can be hosted on Fly together with the app itself.