On Sep 28, 11:12 am, Idris <[email protected]> wrote: > Why not just upload the file straight to S3 (I recommend not going > through paperclip, but instead going straight to S3, so you don't hold > up the dyno). Then when the upload finishes, kick off a background > job to read the image off S3, process it, and save the processed > image.
This is exactly what I'd recommend if you want something scalable. There are a few flash-based plugins that will even let you upload directly to S3 so your dyno is not tied up. I have used this to allow users to upload videos. That said, if you are just dealing with images, setting up direct-to- s3 uploading (and all the callbacks and background processing associated with it) can be way too much development time. It won't scale, but for small-to-medium sites, using paperclip and having the dyno resize your images then upload to S3 will work just fine. Paul -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
