Concern about FastCGI deprecation

[Shawn H]

While my preference would be to run Django on Linux Apache and run mod_wsgi, I'm limited to a IIS web server for production. What options will those of us stuck in this situation have, now that FastCGI support is being removed? Please provide a lifeline to those of us who love Django but have to use IIS. Thanks.

[Javier Guerra Giraldez]

On Tue, Sep 2, 2014 at 2:15 PM, Shawn H <shawn....@gmail.com> wrote:
> Please provide a lifeline to those of us who love Django but have to use
> IIS. Thanks.

FastCGI isn't a Django concern, as it is a WSGI-only framework (like
most Python frameworks). flup used to be a reasonable FastCGI WSGI
container, but it's no longer supported, so it's unreasonable to ask
the Django foundation to support it.

the question is: what options are there to run WSGI under IIS? my
first guess would be any HTTP-WSGI container (gunicorn?) and set IIS
as a proxy.

--
Javier

[James Bennett]

On Tue, Sep 2, 2014 at 3:08 PM, Javier Guerra Giraldez <jav...@guerrag.com> wrote:

FastCGI isn't a Django concern, as it is a WSGI-only framework (like
most Python frameworks).   flup used to be a reasonable FastCGI WSGI
container, but it's no longer supported, so it's unreasonable to ask
the Django foundation to support it.

the question is: what options are there to run WSGI under IIS?  my
first guess would be any HTTP-WSGI container (gunicorn?) and set IIS
as a proxy.

The answer is: copy/paste the flup bridge code from an old version of Django.

Nothing in Django attempts to detect use of FastCGI and crash when discovered. Rather, Django just no longer ships a FastCGI-to-WSGI bridge, so deployments which use FastCGI will need to provide their own.

[Shawn H]

Thank you both for the response, and the explanation of why the FastCGI support was deprecated. I will look into both of your suggestions, though I will also look to see if http://pytools.codeplex.com/wikipage?title=wfastcgi (which I found after posting this question) will work. Microsoft apparently uses in this in the Azure environment, so it may be the best approach for ongoing support.