My understanding is summarized on the output Mongrel gives when you start it:
** Signals ready. TERM => stop. USR2 => restart. INT => stop (no restart). ** Rails signals registered. HUP => reload (without restart). On 4/18/06 11:52 PM, "Dan Sketcher" <[EMAIL PROTECTED]> wrote: HUP being a "reload" is done as a soft internal kind of thing, so if you're moving directories around then it won't pick that up. You want USR2. Zed > Hey all, > > Has anyone out there got Mongrel deployments working with Capistrano? > > I've had a crack at setting it up, and I've found that after a > deployment (with updated symlinks) that a mongrel restart does not > pick up the new deployed site. It seems to me (in my linkted > experience) that the HUP that is sent to mongrel does not re-evaluate > the ./current symlink that Cap puts in to the appropriate release. If > I do a mongrel restart from _outside_ the ./current dir by providing > the -e option to mongrel, all is well. The result of all this is that > a :restart from Capistrano that just sends a HUP is not effective, but > I am not sufficiently familiar as yet with the pathing stuff in Cap to > get it going another way. > > Anyway, if someone has some cleverness that I am missing, it would be > greatly appreciated! > > Cheers, > Dan > > _______________________________________________ > Mongrel-users mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/mongrel-users _______________________________________________ Mongrel-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/mongrel-users
