while I don't advocate developer's hitting production .. it happens, and can make life easier
may I suggest you just set up a sudo command to bounce the server? I would also make it so you have 2 code-bases and the command would switch to the 'fresh' one. ie the script would do something like cd old svn up cd .. mv old tmp mv running old mv tmp running apachectl restart and of course have a corresponding 'backout' command which reverses it for when the developer screws up On 08/07/2006, at 7:23 AM, x0nix wrote: > >> Um, you earlier stated that the problem was that you have >> "PythonAutoReload On". That's not on your production server is it? >> Generally, that setting would only be used in a testing environment. > > Oh I didn't notice that it should be used only for testing, thanks for > info. > >> And do you really update you production server with each little >> modification? Wouldn't it be more practical to update the production >> server once a day or so. That way, only one developer would be >> restarting apache only once a day. The process could perhaps even be >> automated to run at a low traffic time. > > I was thinking about the same (cron) solution, seems the best > available. > > [I still don't think that one day is adequate response time, but with > possibility of Apache restart it could be sufficient] > > Thank you all for answers > > x0nix > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
