Matt Haggard wrote: > I'm (in the process of) using pylons in a production environment and > still have a few questions: > > 1) Do I really have to restart the server every time I make a change > (controller/model)? I can foresee making many changes and some which > require immediate attention, but restarting the server in the middle > of the day would not be an option. So, do I have to make changes at > night? Is there no way for the server to adopt the changes without > killing all connections?
When restarting any connections in-progress will be completed, and new connections will be rejected. If you are using a frontend like Apache that has something to retry connections, no actual requests will fail during a restart. > 2) The system will be composed of multiple apps... (perhaps as many as > 20 or more) so would it be better (if I need to restart after every > change) to have all the apps served by their own servers? I mean, is > it better to have 20 instances of the paster server if uptime is such > a priority? You might want those apps separate to make them more maintainable (e.g., avoid breaking app A when you upgrade app B). I'd try to get a setup where restarts don't lose any connections, then for uptime it's not an issue. If you want to test how it's working, probably you could fire up something like ab (the apache benchmark app) and see if everything works right when you restart your app during the run. -- Ian Bicking : [EMAIL PROTECTED] : http://blog.ianbicking.org --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
