Ok, good. That reload mechanism won't work with most people's Capistrano deploys anyway because the new app code is in a different working directory.
I'll make a ticket to remove it for 1.2. Evan On Fri, May 23, 2008 at 1:12 PM, Zed A. Shaw <[EMAIL PROTECTED]> wrote: > On Fri, 23 May 2008 13:03:58 -0400 > "Evan Weaver" <[EMAIL PROTECTED]> wrote: > >> This line is for the reload signal that always says "Might not work >> well" at startup, right? Did it used to work well? If nobody really >> uses it might be better to remove it; otherwise, we should try to get >> it to work well (which can be hellish with Rails' dependency system). > > It used to work OK, but it relies on the internal Rails reload > mechanism used for development mode. It was intended to let you run > your rails app in production and then hit it to kick it over rather > than wait for a reload. > > I'd say these days it's not needed and it risks running into changes in > how Rails operates. Probably worth dropping. > > -- > Zed A. Shaw > - Hate: http://savingtheinternetwithhate.com/ > - Good: http://www.zedshaw.com/ > - Evil: http://yearofevil.com/ > _______________________________________________ > Mongrel-users mailing list > Mongrel-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users > -- Evan Weaver _______________________________________________ Mongrel-users mailing list Mongrel-users@rubyforge.org http://rubyforge.org/mailman/listinfo/mongrel-users
