Hi everyone,
I’m new to Django and to this group.
I’ve been struggling getting Django 1.3 to work under Windows 2008 R2 and IIS7 for about a week or so and I’ve just found that some of the .py files required by PyISAPIe refers to some signal dispatching methods which were removed from Django long ago. So it doesn’t work at all with Django 1.3. Instructions for using the isapi_wsgi are indecipherable as are instructions for FastCGI.
Before I go any further with Django under IIS, I would like to ask the community what their recommendation is for running Django under IIS? What “glue” is preferred for connecting Django 1.3, Python 2.7.1 and IIS on Windows Server 2008 R2?
Apache on windows is an option, but not a preferred one since IIS is far easier for us to make production-ready.
Thanks in advance,
-David Lurton
So far our experiences have been great! Thanks for this making this
tool. Do you know when it will be out of beta and what the price will
be when it's purchasable?
Also, does this beta version have any kind of expiration? We know it's
beta and not production ready every options that we've tried so far
experienced so far (configuration of PyISAPI, FastCGI, and isapi_wsgi)
has terrible documentation and no automated installation or is simply
out of date and doesn't work with Django 1.3. With zoo however we had
our (3rd party) Django application working within a day.
We would have deployed this on a Linux box but unfortunately our
operations team's only core competency is with Windows. We were working
for a week with the other three options, so the timing of your beta
release was quite serendipitous indeed!
Thanks again,
-David Lurton
Hello David.
--
You received this message because you are subscribed to the Google
Groups "Django users" group.
To post to this group, send email to django...@googlegroups.com.
To unsubscribe from this group, send email to
django-users...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.