Iain Duncan wrote: > >>how do you handle changes on a site which is already online (talking > >>about changing models and/or views)? > > > > > > I typically maintain a duplicate setup on a testing machine (in my > > case, a laptop running Linux) and use that for development and > > testing, then when I know I've got the bugs worked out I deploy the > > changes in production. > > This is my first time using mod_python in production, how do you handle > the need to restart apache? I have to figure this stuff out for a > clients sight this week and don't want any surprises! =) > > Iain
sudo /etc/init.d/apachectl graceful This will restart apache after it finishes serving current requests -- Wade Leftwich Ithaca, NY --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" 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/django-users -~----------~----~----~----~------~----~------~--~---
