voltron wrote: > What actually is recommended by the Pylons gurus? The monitor and > reload functions are there for a purpose, are they to be used in > production?
--reload does something different than the other tools. And you shouldn't use it in production, it's slow. (If someone wanted to write a faster implementation based on one/many of the file-change notification libraries, then it could probably be used in production.) --monitor came about because I was annoyed with dealing with the options on a specific system, and in terms of implementation it was just a minor extension of --reload. But if you really want this functionality right now I'd recommend using one of the other options. I am using --monitor on a couple production processes, but only because I'm also keeping an eye on them. And only from PasteScript trunk. (I guess I should make a release, actually). -- Ian Bicking | [EMAIL PROTECTED] | http://blog.ianbicking.org | Write code, do good | http://topp.openplans.org/careers --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
