On Mar 24, 5:04 pm, Graham Dumpleton <graham.dumple...@gmail.com> wrote: > Use Apache/mod_wsgi and the documented method of running a WSGI > application in a specific daemon process in a autoreloading > development mode. You could even have both the production and > development instances under same Apache under different hosts, with > only development instance having autoreload enabled. Would be much > simpler as you don't have to muck around with the supervisor software. > Also basically otherwise the same set up as your production > environment and so better test as far as making sure everything works > properly. See: > > http://code.google.com/p/modwsgi/wiki/ReloadingSourceCode > > http://blog.dscpl.com.au/2008/12/using-modwsgi-when-developing-django... > http://blog.dscpl.com.au/2009/02/source-code-reloading-with-modwsgi-o...
I like mucking around with supervisor software. But this is clearly a superior approach. Thanks for the links! Dave --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
