Re: Is it possible to use CarrierWave on Heroku without relying on cache?
Thanks Mark! It's not the ideal solution since the gem is starting to look stale, but it's a great place to start for the basics On May 25, 12:33 pm, Mark Ellul mark.el...@gmail.com wrote: There is an s3 gem upload gem which allows straight from the browser to s3 uploads... gem 's3_swf_upload', :git = 'git://github.com/nathancolgate/s3-swf-upload-plugin' It uses a swf to do it though! -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Is it possible to use CarrierWave on Heroku without relying on cache?
We would like to use CarrierWave for handling our uploads on Heroku, but it needs to cache locally to the /tmp directory. I am concerned that if many users are uploading at once, the directory could fill up and hit the maximum disk size limit imposed by Heroku. Is there a way to upload directly to S3 without relying on CarrierWave's caching feature? Has anyone done this successfully? -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.