Benjamin Curtis wrote: > On Wed, Oct 1, 2008 at 12:05 PM, Neil Cauldwell < > [EMAIL PROTECTED]> wrote: > >> > >> > On Sep 2, 8:45 am, Neil Cauldwell <[EMAIL PROTECTED]> >> >> Thanks Keith, I'm almost 100% done with implementing Paperclip, I just >> need to mock the calls to S3 and make at a background worker for pushing >> to S3 instead of tying up mongresl (the later won't be so easy). >> >> ... > > > Both backgroundjob and spawn are great ways to do this. I use both to > great > affect to do the same thing. > > -- > Benjamin Curtis > http://railskits.com/ - Ready-made Rails code > http://catchthebest.com/ - Team-powered recruiting > http://www.bencurtis.com/ - Personal blog
Thanks. I was thinking it would mean storing locally and moving to S3 in the background; someone seems to have taken the same approach in a thread on the Paperclip google group (although there's 0 responses so I don't know how they got on with it); http://groups.google.com/group/paperclip-plugin/browse_thread/thread/8af52cc25cd97d02/05221d1a7254601d?lnk=gst&q=background#05221d1a7254601d There's an interesting presentation on starling, workling, spawn etc (among other background workers) which got me thinking about going with something other than backgroundrb; http://www.slideshare.net/purzelrakete/railsconf-berlin-04092008-presentation?src=embed ...but I just got off the phone with an engine yard account manager for my app and I'm waiting to see what their devs have to say about. Apparently they have quite a few apps pushing content to S3, so it's something they can help out with; I'm not sure how far they can get in separating out processes to async processes (I have tons of specs, but still), but maybe I won't need to write it all from scratch. I think this would make a pretty good screencast for someone to make (and charge for). I'd pay $5 - 10 to see how a pro installs a user avatar (probably the most common image upload), sets all the right defaults for paperclip, makes it all secure, sets up decent spec coverage, asyncs it with S3 (again, which good spec coverage) and makes it manageable over dev, test, staging, production environments. I've done most of it, but, I would still pay to watch an expert implement it using best practices. -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ 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 [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
