Geek Answers Handbook

Image correction when uploading to s3, only for production. (carrier, motor)

I use a carrier to load images in amazon s3. This works fine during development, but not when I click it on my server (trial version for cloud computing).

The process works fine, no errors occur, and the link is returned. However, the actual image is damaged, one way or another.

Here is one, for example: https://s3.amazonaws.com/ZenBucket/uploads/goal/photo/30/guinness-toucan.jpg

Can someone tell me how damaged it is or what it can do?

Edit: The first attempt to upload an image after deployment always seems to fail 500, but the error does not appear in the log. Not sure if this is relevant.

Edit2: Also seems to be happening with a dragonfly stone instead of a carrier.

thank

+5
source share
3 answers

It seems that the problem with gzip compression in jRuby (possibly with https) has been resolved. If someone needs version numbers from my stack, I can oblige.

0
source

If this happens only in the first image after deployment, I suspect that your application is still loading (or at least some working), which leads to high processor utilization and slowdown of the loading process, which may lead to a timeout and damage to the image at the same time.

, Engine Yard , . "" , , .

EC2 ​​ , .

0

/ EngineYard, : http://www.engineyard.com/blog/2011/a-gentle-introduction-to-carrierwave/ : http://docs.engineyard.com/use-carrierwave-and-optionally-fog-to-upload-and-store-files.html

Is your "fog" publicly available for the "false" or the "true"? If this is false, check this thread as you will need to use the authenticated_url property instead of the return property: http://groups.google.com/group/carrierwave/browse_thread/thread/2f727c77864ac923

0
source

More articles:


All Articles