OK, fair enough. I'll leave it commented out. On 7/23/06, Zed Shaw <[EMAIL PROTECTED]> wrote: > On Sat, 2006-07-22 at 17:38 -0600, Kevin Williams wrote: > > I coded up a handler, using the MongrelDbg module to help me debug. I > > deployed my code and found it royally broken in production because it > > couldn't include that module. > > > > What's the best practice for having MongrelDbg in code and not > > breaking in different environments? Is this just a bug? I commented > > out all my MongrelDbg usage and redeployed, and it works now. > > > > Actually the best practice is to not actually use that in your code. > It's pretty much internal Mongrel code only used when you *temporarily* > put Mongrel unto -B (debug) mode. > > The main nasty part of that module is the object tracking stuff, which > I'm actually rewriting with something much lighter. > > > -- > Zed A. Shaw > http://www.zedshaw.com/ > http://mongrel.rubyforge.org/ > http://www.railsmachine.com/ -- Need Mongrel support? > > _______________________________________________ > Mongrel-users mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/mongrel-users >
-- Cheers, Kevin _______________________________________________ Mongrel-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/mongrel-users
