Avoiding killall

When I started Rails Development, I needed to use ‘killall -g
dispatch.fcgi’ whenever I made a change to a Model to see the change on
my website. Now it seems I need to do this to see any change to the
Controller as well.
Any ideas of what I am doing wrong???

On Wed Jun 28, 2006 at 11:07:30PM +0200, battreal wrote:

When I started Rails Development, I needed to use ‘killall -g
dispatch.fcgi’ whenever I made a change to a Model to see the change on
my website. Now it seems I need to do this to see any change to the
Controller as well.
Any ideas of what I am doing wrong???

are you running in production mode while doing development? thats what
it sounds like

if you use eg, initng, and mongrel, you can just paste something like
this into /etc/initng/daemon/mongrel.i

daemon daemon/mongrel {
need = system/bootmisc;
use = system/static-modules system/coldplug;
require_network;
exec daemon = /usr/bin/ruby18 /usr/bin/mongrel_rails start -c
/var/www/app -p 80;
}

and issue ‘ngc -r mongrel’. similar for apache would be ‘apachectl
restart’. in development mode this is only necessary in a few cases like
changing contents of the vendor/ and maybe lib/ or config/ directories…

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs