Get script/runner back in Rails 3

May 19, 2010

EngineYard’s chef recipe for DelayedJob requires script/runner. To use this recipe with Rails 3 I’ve just made script/runner for Rails 3. Here is the code:

Edit: Fix for rails 3.0

. Bookmark the permalink. Post a comment or leave a trackback: Trackback URL.

5 Comments

Damien

Posted May 19, 2010 at 22:20 | Permalink

Wouldn’t the best idea to be to change the chef recipe instead of adding this ?

Reply
- Philippe Creux
  
  Posted May 19, 2010 at 22:54 | Permalink
  
  Thanks for your comment Damien! We considered this solution actually. :)
  
  Their chef recipe creates a monit file that runs “/engineyard/bin/dj start/stop“. The dj script runs the command “script/runner -e production 'Delayed::Job.start'” or so.
  
  It would have been longer to create a homebrewed chef recipe + monit + dj-like than adding script/runner to our rails 3 app. As soon as they make their dj script compatible with rails 3 we can get rid of script/runner.
Jordan Brough

Posted December 8, 2010 at 13:44 | Permalink

#!/usr/bin/env bash
rails runner "$@"

might be a bit more robust?

Reply
Yuval

Posted December 12, 2010 at 16:30 | Permalink

Just ran into this issue after upgrading from Rails 2.3.5 to Rails 3, but unfortunately this hack doesn’t seem to have fixed the issue. I used to get “Execution failed” messages and now I just get “Does not exist.”

Reply
Davis Laib

Posted June 18, 2011 at 02:43 | Permalink

Yeah, it is too hard for Bing or Yahoo to compete with Yahoo in Search Engine market. Maybe I simply expect Fb’s ambition may make the industry far more intriguing.

Reply