On Fri, Apr 11, 2014 at 3:31 AM, anton <anto...@gmx.de> wrote: > Russell Keith-Magee wrote: > >> On Wed, Apr 9, 2014 at 1:09 AM, anton <anto...@gmx.de> wrote: >> >>> Hi , >>> >>> I use: >>> - windows 7 64 bit >>> - python 2.7.6 (32bit) >>> - apache 2.4.9 (32bit vc9 build from apachelounge) >>> - django 1.6.2 >>> - flup for fcgi ( noted as prerequisite in django docs) >>> >>> I use flup for running django as fcgi, >>> unfortunately I have the problem that > .. snip snip cot off >>> >>> So what is the future for django and fcgi on windows, >>> or will this functionality be integrated in django 1.7 (would be nice). >>> >> >> There *is* no future for FCGI on Django, on Windows or any other operating >> system. We've deprecated support for FCGI, and will be removing support >> for FCGI in the Django 1.9 release. >> >> Third party projects may choose to maintain support for FCGI wrappers to >> Django, but that will be outside the official project. >> >> If you want to deploy a Django site, you should be using WSGI. A wide >> range of servers and service providers support WSGI; However. I can't >> comment on which ones are especially good or bad under Windows. >> >> Yours, >> Russ Magee %-) >> > > Hi Russ, > > thanks for the advise, I didn't know that fcgi is deprecated.
To be clear - FCGI isn't deprecated; Django's support for FCGI is deprecated. I'm sure FCGI will continue to be used; it just won't be used or actively supported by Django. > I thought its nicer to use so I can have different > apps ( = parts of my web intranet portal) running as > - complete independent django instances > - with different ( = independent) databases > > So if I have to do some more critical changes in one part of my > web portal I can shutdown only the one fcgi service do the work > and start it later again. > > -> the rest of the services are not touched. > > I am not sure if this is possible with wsgi. It certainly is - that's exactly what WSGI was designed to achieve. Each "site" or "service" can have a separate WSGI definition inside a single web server; each WSGI definition can point to a different database, and/or a different Django instance, or even at a site implemented in a different web framework. > I use apache 2.4.9 on windows with the modwsgi > but I am unsure about the modwsgi for apache > (http://code.google.com/p/modwsgi/) > because the last code change is from october 2012 > so it seems a little bit "abandon ware" It hasn't been modified because it hasn't needed modification. To the best of my knowledge, Graham Dumpleton is still actively supporting mod_wsgi. > (I looked at uwsgi, but it runs only on Linux/unix) > > Is there any (even "semi") official best way to run django on windows > (which is up to date)? > Or is windows officially not supported for production? *Django* supports Windows; however, I'm not in a position to provide advice on the selection of production web servers under Windows. My completely uninformed suggestion would be to use Apache, but that's only based on the fact that it has a long history. There may well be better options. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAJxq848a7_NA5JFUYeihak%2BYkkzpOhe1%3DWj80h701bGQE-cWDg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
