Yes, I've seen the Heroku gem inclusion idea (which seems like a damn good one for me). This does seem like a killer feature for heroku though, so kinda curious as to why there aren't any published "best practice" ways to do it from the heroku mother ship ? (and for some reason searching on this group didn't turn up any posts you alluded to... =< ).
So, can you qualify the "feint of heart" comment ? Just wondering. Being foolhardy instead, I should probably be informed... =] BTW, the use case in particular would be punting something to a delayed_job and then sicking a whack of ramped up workers on it till it was done. Dynos would be interesting too, so are you advising checking an increasing queue depth to tell when this needs to happen ? Anyhow, thank you very much Oren. ciao ! Daryl. On Jan 30, 5:45 am, Oren Teich <[email protected]> wrote: > There's been some discussion on the list before about how to achieve this. > It's possible, but not for the feint of heart. You can include the heroku > gem and just call "heroku dynos X", or look at the heroku gem source code on > github to see the API calls we make. http://github.com/heroku/heroku > Search the archives for HEROKU_QUEUE_DEPTH as well. > > Oren > > On Thu, Jan 28, 2010 at 9:03 PM, Daryl <[email protected]> wrote: > > +1. I was just about to ask if anyone had some code samples of doing > > this we could study (or point at them if we're just being dense with > > google searches). > -- You received this message because you are subscribed to the Google Groups "Heroku" 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/heroku?hl=en.
