So files are left locally in the imagecache folder and also sent to S3 cloudfront. So that means every image lives in 2 places? So thousands of images could get really expensive on your hosting bill having to pay for storage in both places. Is there a reason for this or a way around it?
thanks

also, deleting a node doesn't delete the image file from S3, just the local file.

Comments

doublejosh’s picture

doublejosh commented

I understand the concern, but...

- you'd need a scaled version and the original anyhow.
- storage is must cheaper than processing, so having files ready is always best.
- if you actually have enough files to worry about storage... you don't have a problem, you have a successful business.

The deleting issue is definitely a "bug" though.

jordanmagnuson’s picture

jordanmagnuson commented

I understand the value of having local copies of the files, but disk space can indeed become an issue... would it be possible to have an option to delete local files after the images have been moved to cloudfront?

jordanmagnuson’s picture

jordanmagnuson commented

Also, can I get a clarification on this, as far as what is being kept on the local server?

Let's say I have an image, "myimage.jpg", and I have two image_cache presets that I'm displaying using cloudfront:

print cloudview_theme_imagecache('small_thumb', 'myimage.jpg', 'just a test image', 'test image');
and 
print cloudview_theme_imagecache('big_thumb', 'myimage.jpg', 'just a test image', 'test image');

Obviously the original image, myimage.jpg is being kept on the local server... is it also being kept on amazon's cloudfront servers?

What about the two presets? Obviously they're being kept on amazon's cloudfront servers, but are they also being kept on the local server, along with the original image (as per traditional imagecache functionality)? I'm asking, because it seems that the thumbnails would NOT need to be kept on the local server at all.

Thanks for any clarification!

hozt’s picture

hozt commented
Assigned: Unassigned » hozt

Currently all versions of the images are kept on the local server and only the imagecache presets enabled with cloudfront are sent to the cloudfront servers.

The local imagecache files do not need to be kept locally. Imagecache will automatically regenerate an image that has been removed from the local filesystem so as part of the upload process we should be able to delete the local file.

I will try to get this feature in the dev version in the next couple of days.

hozt’s picture

hozt commented
Status: Active » Closed (won't fix)