I can't help with starling. If you're in the position to try out delayed_job, you may want to. We ran it on Naughty America's servers with good outcome. If you're not able to switch, I'm sorry I've been no help :)
Martin Emde Tw: @martinemde On Mon, Aug 24, 2009 at 8:36 PM, Nick Zadrozny <[email protected]> wrote: > On Mon, Aug 24, 2009 at 17:06, [email protected] <[email protected]>wrote: > >> I know the biggest gotcha is running starling on port 15151 and I'm 99% >> sure I'm doing this. > > > Are you only talking to Starling from localhost? If not, are you sure you > opened that port in your server's security group configuration? > > Have you tried popping messages off the queue from irb to verify that your > messages are getting to Starling in the first place? > > Also, have you considered delayed_job? Starling is nice and minimal, and I > used it once upon a time, but these days, delayed_job is my usual first > choice for running jobs asynchronously. (And my second choice is actually > AMQP and RabbitMQ for serious message passing.) > > -- > Nick Zadrozny > > > > > --~--~---------~--~----~------------~-------~--~----~ SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby -~----------~----~----~----~------~----~------~--~---
