Hey All, I just wanted to get other peoples take on problems when running merb in production? Just as Rails used to do, the mongrels tend to get heavy/unresponsive over time so need a good kicking by a watcher daemon like god or monit. However, I have had serious problems getting God to restart the process, as the "merb -k <port>" command doesnt appear to work reliably and it cant kill off the old merb successfully so restarting the new one fails :'(
What have other people experienced? How are you tackling these problems? Many thanks Tim _______________________________________________ Merb-devel mailing list [email protected] http://rubyforge.org/mailman/listinfo/merb-devel
