Tuesday, February 1, 2011

Re: switch to apache

On Tue, Feb 1, 2011 at 4:38 AM, Ethan Yandow <flibitboat@gmail.com> wrote:
> Alright, im not really sure how to explain this but here goes.  I just
> got Django running on apache.  I got apache to work in the same way
> that the development server does.  The only problem is that when I
> modify a django file (a template or a view or anything)  Django/apache
> doesn't seem to notice the change, but sometimes it does notice the
> change but reverts back to the old file and what not.  Can anyone help
> me out with this?  Also, I need to write a small chat client thing
> using django and openfire, does anyone have any experience donig
> that?  Thanks alot guys!!
>
> Ethan Yandow
>

Only the development server (mostly) reliably notice when source code
change. If you deploy to Apache using mod_wsgi in daemon mode, then
you it can also notice when you make changes [1].

For other modes, no, you can't. Restart Apache to consistently see
your changes. Apache will notice* when your template files or media
change, but not your application code, which can lead to inconsistent
behaviour if you do not restart.

Cheers

Tom

* This is complete nonsense, Apache doesn't notice anything at all,
but django will load templates from disk, so updating the templates on
disk will lead to them being used immediately, whilst the new code
won't be.

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

--
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+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.

No comments:

Post a Comment