Comments on: Get script/runner back in Rails 3

By: Davis Laib

Davis Laib — Sat, 18 Jun 2011 10:43:33 +0000

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.

By: Yuval

Yuval — Mon, 13 Dec 2010 00:30:16 +0000

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

By: Jordan Brough

Jordan Brough — Wed, 08 Dec 2010 21:44:13 +0000

#!/usr/bin/env bash

rails runner "$@"

might be a bit more robust?

By: Philippe Creux

Philippe Creux — Thu, 20 May 2010 06:54:33 +0000

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.

By: Damien

Damien — Thu, 20 May 2010 06:20:42 +0000

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