On 3/27/07, walterbyrd <[EMAIL PROTECTED]> wrote: > Is that post correct? You have to restart the server whenever you make > a change to the django code?
It depends on the deployment strategy you use. If you use mod_python efficiently, yes, you'll have to restart Apache between code changes. If you use FastCGI, you may only have to "touch" the .fcgi file to tell it to reload the files. In the real world, this isn't a huge problem, as Django comes with a development server that automatically reloads your code for you. The performance advantages of keeping code in memory at the production-server level far outweigh the convenience of being able to make changes without restarting. Adrian -- Adrian Holovaty holovaty.com | djangoproject.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
