Carrierwave documentation includes this tip for uploading large files. Inside
your uploader, add these two methods (they say)
def move_to_cache
true
end
def move_to_store
true
end
to make the uploads work more efficiently. This is true, it does work -- as long
as you aren''t trying to do anything with versions or other processing.
If you do, then the upload will only ever work in a create method, not an
update.
Can anyone suggest a way where I may be able to take advantage of the one-pass
upload on create, but still manage to access the stored file as a file (the
result of move_to_cache, I believe) when I need to?
Thanks in advance,
Walter
--
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit
https://groups.google.com/d/msgid/rubyonrails-talk/67DE5E79-C15D-4CEE-AB4B-E8848D06DD17%40wdstudio.com.
For more options, visit https://groups.google.com/groups/opt_out.
