8

I'm running a Django app on Apache + mod_python. When I make some changes to the code, sometimes they have effect immediately, other times they don't, until I restart Apache. However I don't really want to do that since it's a production server running other stuff too. Is there some other way to force that?

Just to make it clear, since I see some people get it wrong, I'm talking about a production environment. For development I'm using Django's development server, of course.

ibz
  • 44,461
  • 24
  • 70
  • 86

4 Answers4

15

If possible, you should switch to mod_wsgi. This is now the recommended way to serve Django anyway, and is much more efficient in terms of memory and server resources.

In mod_wsgi, each site has a .wsgi file associated with it. To restart a site, just touch the relevant file, and only that code will be reloaded.

Daniel Roseman
  • 588,541
  • 66
  • 880
  • 895
  • I'm a bit scared of this XXgi things after all the trouble I had with FastCGI (sure, it was Lighttpd, but still): http://stackoverflow.com/questions/393637/django-fastcgi-randomly-raising-operationalerror. Didn't know wsgi is the recommended way to deploy Django now. It used to be mod_python, right? Anyway, I'll look into it. Thanks! – ibz Jul 03 '09 at 10:12
  • s/this things/these things/ :) – ibz Jul 03 '09 at 10:13
  • 2
    As noted elsewhere, you must use mod_wsgi daemon mode to get feature whereby a reload will occur when WSGI script file is touched. – Graham Dumpleton Jul 03 '09 at 10:20
  • @ibz: mod_wsgi is so different from fastcgi that they are not comparable in any way. – S.Lott Jul 03 '09 at 12:14
  • 1
    Note that (as Graham Dumpleton mentions below) the touch-.wsgi-file-to-restart only works in daemon mode, not embedded mode. – Carl Meyer Jul 03 '09 at 21:13
4

As others have suggested, use mod_wsgi instead. To get the ability for automatic reloading, through touching the WSGI script file, or through a monitor that looks for code changes, you must be using daemon mode on UNIX. A slight of hand can be used to achieve same on Windows when using embedded mode. All the details can be found in:

http://code.google.com/p/modwsgi/wiki/ReloadingSourceCode

Graham Dumpleton
  • 57,726
  • 6
  • 119
  • 134
1

You can reduce number of connections to 1 by setting "MaxRequestsPerChild 1" in your httpd.conf file. But do it only on test server, not production.

or

If you don't want to kill existing connections and still restart apache you can restart it "gracefully" by performing "apache2ctl gracefully" - all existing connections will be allowed to complete.

tefozi
  • 5,390
  • 5
  • 38
  • 52
  • "apache2ctl gracefully" sounds like a neat thing. Will definitely look into that, even though it's not exactly what I was looking for. Thanks for the tip! – ibz Jul 03 '09 at 10:10
-1

Use a test server included in Django. (like ./manage.py runserver 0.0.0.0:8080) It will do most things you would need during development. The only drawback is that it cannot handle simultaneous requests with multi-threading.

I've heard that there is a trick that setting Apache's max instances to 1 so that every code change is reflected immediately--but because you said you're running other services, so this may not be your case.

Achimnol
  • 1,551
  • 3
  • 19
  • 31
  • Thats "MaxRequestsPerChild 1" set in httpd.conf as told by zdmytriv, but DO NOT do this for site handling any load. – agiliq Jul 03 '09 at 09:22