Hi ! I developed a small Website querying some other sites in background like a "cron". The queries are handled in a separate thread that I can start and stop when I want from a simple web-interface. It works great on my development environment, when I launch the website using the "python manage.py runserver" command.
But when I put the site on a production environment, using mod_wsgi (or mod_python) following the steps described on Django's website, it appears that the website is launched each time a user is querying it, so the thread does not persist between them. So I managed to run the site with a reverse proxy handled by Apache with mod_proxy ( here is my config file if you are interested http://dpaste.com/hold/146080/ ). I simply run the django's integrated server on the port 8000 and it works as expected. I need your point of view of that approach of the problem : is it good enough for a production website ? (fast, stable etc...) My website is not intended to a large public, but I am curious about that, and - if this is a viable solution -, why not document it as an alternative of the other deployment solutions ? Thank you, AlK
-- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@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.
