Get script/runner back in Rails 3

5 Comments

1. 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.

2. Jordan Brough
   Posted December 8, 2010 at 13:44 | Permalink

   
#!/usr/bin/env bash

   rails runner "$@"


   might be a bit more robust?

   Reply
3. 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
4. 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