If considering mod_wsgi due to its reloading ability, ensure you read: http://code.google.com/p/modwsgi/wiki/ReloadingSourceCode
http://blog.dscpl.com.au/2008/12/using-modwsgi-when-developing-django.html http://blog.dscpl.com.au/2009/02/source-code-reloading-with-modwsgi-on.html to understand what modes it works in and what it gives you. Graham On Mar 10, 12:45 pm, Dave Fowler <davefow...@gmail.com> wrote: > Thanks, I'm currently under mod_python... maybe I should switch. > > On Mar 9, 8:33 pm, Alex Gaynor <alex.gay...@gmail.com> wrote: > > > On Mon, Mar 9, 2009 at 8:31 PM, Dave Fowler <davefow...@gmail.com> wrote: > > > > I'm running Django with memcached on EC2. We frequently turn on or > > > off different servers with memcached running on each. > > > > To configure your memcached the docs suggest you list them in your > > > settings file: > > > > CACHE_BACKEND = 'memcached://172.19.26.240:11211;172.19.26.242:11211/' > > > > The only problem with this is that every time I add or remove a server > > > I have to edit and restart all of my django instances. > > > > Is there another way to control the memcached settings? > > > > Do I even need to restart the apache instances if my memcached > > > settings change? > > > > Thanks! > > > If you're deployed under mod_wsgi I believe touching the WSGI file will > > cause it to reload the files. > > > Alex > > > -- > > "I disapprove of what you say, but I will defend to the death your right to > > say it." --Voltaire > > "The people's good is the highest law."--Cicero --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
