#8742: Windows support of FastCGI feature
------------------------------------+---------------------------------------
Reporter: anonymous | Owner: nobody
Status: new | Milestone:
Component: Uncategorized | Version: SVN
Resolution: | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
------------------------------------+---------------------------------------
Comment (by snaury):
I can confirm that flup works on Windows and Apache, just not the way most
people expect (due to principal differences between files and sockets on
Windows). To make it work, you need to start your server like this in your
dispatch.fcgi:
{{{
from django.core.servers.fastcgi import runfastcgi
runfastcgi(protocol="fcgi", method="threaded", daemonize="false",
host="127.0.0.1", port=port)
}}}
Then in your httpd.conf you will need to make apache aware of your server:
{{{
FastCgiExternalServer <path-to-your-wwwroot>/dispatch.fcgi -host
127.0.0.1:<port>
}}}
Of course with this setup apache won't start your fastcgi server for you
(and frankly, with the way python (or flup, I'm not sure) handles signals
on Windows you DON'T want apache to start python servers for you, as it
won't be able to kill them afterwards), you'll need to do it yourself
separately. I, for example, run my fastcgi server as a Windows service
(using win32service), which is even better since with this setup apache
and fastcgi servers can run as different users.
--
Ticket URL: <http://code.djangoproject.com/ticket/8742#comment:5>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
