> So, wouldn't I have the same issue with DJ and my process exceeding > 30s?
What I've been doing is storing the files on S3, and then pulling them down to the tmp directory on demand when my DJ process requests them. All you have to do to copy a file from S3 to tmp (with Paperclip) is: @model_with_attachment.file.to_file You could then open it for processing with: File.read(@model_with_attachment.file.to_file) Then you can delete the file from S3 when you're done with it. The best thing about using S3 is that you'll always know exactly where the file is, no matter which DJ process is using it. On Jan 8, 2:19 pm, Karl <[email protected]> wrote: > On Jan 8, 12:10 pm, David Dollar <[email protected]> wrote: > > > This wouldn't work on Heroku because even though it's in a different > > thread it's still the same request, and we only allow requests to go > > for 30s. This would tie up your dyno for the background request. > > So, wouldn't I have the same issue with DJ and my process exceeding > 30s? > > BTW, when I have run this processing within the current request, and > it has exceeded 30s, I have not seen any errors or issues. Everything > appears to processed successfully.
-- 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.
