No, I never did work this out, had to move on and the solution in place (in production) is sub-standard as a result.
Walter On Jul 16, 2014, at 12:44 AM, Mark J. Lehman wrote: > Walter, > > I know this is almost 2 years old now, but I'm trying to figure out how to do > the same thing with Carrierwave Direct. Did you ever solve this? If you did, > would you mind posting how? Code snippets are also appreciated. > > On Thursday, August 30, 2012 8:39:02 AM UTC-7, Walter Lee Davis wrote: > > On Aug 30, 2012, at 5:24 AM, tundrax wrote: > >> > >> > >> > >> 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 > > > > 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. > > Sorry, what? > > I was able to make a form containing a single file field which would upload > using Carrierwave _Direct_ to upload to S3 without my server acting as a > middle-man. I was not able to suss out how to combine such a file field with > other fields intended for my server's eyes. > > I was perfectly able to create a single combined form which contained the > file AND its metadata, upload both to my server, and yes, using Fog, store > the file on S3. That's with ordinary Carrierwave, which is lovingly > documented and a drop-in replacement for nearly every other file storage > scheme on Rails. > > The issue, which I still do not understand how to solve without an Ajax > sidecar submitting two forms at once, is how to send part of the data > directly to S3 and the remainder to my server, and maintain a connection > between the two. > > If you can help, I would appreciate it. > > 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+unsubscr...@googlegroups.com. > To post to this group, send email to rubyonrails-talk@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/rubyonrails-talk/a547b6a1-f15b-450e-a1c1-49fc863cee04%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- 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+unsubscr...@googlegroups.com. To post to this group, send email to rubyonrails-talk@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/EC480BF8-F591-46E1-9969-1B7CD2473569%40wdstudio.com. For more options, visit https://groups.google.com/d/optout.
