If you are using wsgi you can touch your wsgi settings file and it has the same effect as restarting apache without a restart most of the time. If you are only running one site on the django installation it isn't any better, but if you are hosting multiple sites and your change is on one settings.py file, for instance, a touch will only effect the site whose wsgi you touch and the other sites will be unaffected. The only way to activate code for all sites is a apache restart. Of course the other option is to throw and error in there. When Django hits a syntax error it will recompile after the next save hoping you have fixed the issue. That isn't very efficient though. :-)
On Feb 3, 9:33 am, Delifisek Tux <[email protected]> wrote: > On Wednesday 03 February 2010 13:30:34 Zygmunt wrote: > > > Hi! > > When i create some changes in my page, i need restart apache server. > > How can i avoid restarting? > > Ummm, it was not a problem. > > It was a feature. Which I realize now. > > (if I understood correctly, please correct me if I was wrong). > > When you run the your code first time, python parses it and stores in > memory. > > In next request it was ready to server. > > Also it was not same kind of PHP OPCODE cache. It was something different. > > It stores your objects too. You did not re cast your objects in every > request... > > So ? > > You have to restart it. -- 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?hl=en.
