Ruby on Rails Thursday, August 30, 2012

Docs say you should use Fog gem

https://github.com/jnicklas/carrierwave#using-amazon-s3

And it doesn't matter what storage you chose, local filesystem, S3 or any other cloud storage.
Your form is submitted and the location of uploaded file, along with other attributes of the model you are editing
are stored in the database. So, you question

>> What I could not work out was how to upload the file to S3 AND other form elements to the model that had Carrierwave mounted on it.

is inappropriate.


On Thursday, August 30, 2012 4:29:25 AM UTC+9, Walter Lee Davis wrote:
I just switched a project from Dragonfly to Carrierwave, specifically to see if I could take advantage of Carrierwave Direct, which uploads large files directly to S3 or another cloud storage.

I was able to make a form containing a single file field that would upload to S3. What I could not work out was how to upload the file to S3 AND other form elements to the model that had Carrierwave mounted on it. I ended up punting and just doing the two-step upload to the server and server stores the file in S3 using regular Carrierwave (not Direct).

Can anyone point me to an example of Carrierwave Direct that incorporates other form fields saved into the same ActiveRecord as the Carrierwave details?

Thanks,

Walter

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msg/rubyonrails-talk/-/yO3w3CjSNXkJ.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

No comments:

Post a Comment