[MapProxy] MapProxy 0.9 under IIS on Windows

[Jörg Schräder]

Hi group!

I'm currently stuck on deploying a mapproxy server in a windows
environment. I would like to run the mapproxy server within a IIS 6.0
server on a Win 2003 R2 machine.
I've already found and installed a FastCGI Module for ISS here
http://www.iis.net/download/FastCGI but now I have no idea how to
configure and run mapproxy as a FastCGI server. Or is there another way
to run mapproxy within IIS?

Thanks for responses,
J?rg Schr?der

[Jörg Schräder]

This is true for the development server which is started via command
line. It includes a standalone http server which can be called from
outside on port 8080.
But for productional environments the mapproxy documentation recommends
a deployment via FastCGI. And why should I install another webserver
which I would have to secure seperately if I already have one.

-------- Original-Nachricht --------
Betreff: Re: [MapProxy] MapProxy 0.9 under IIS on Windows
Von: Milo van der Linden <***@dogodigi.net>
An: J?rg Schr?der <***@hansaluftbild.de>
Datum: 11/10/2010 11:58 AM

I am not completely sure, but in my opinion, mapproxy is a standalone
webserver acting on another port then port 80 (I believe it is 8080 by
default)
No need for modules or whatever on IIS.
So what you would need if you don't want visitors to enter the port
number like: http://someserver.org:8080/ you have to set up some port
forwarding mechanism from IIS

[Milo van der Linden]

My appologies for not replying to list earlier..

Securing the webserver is easy compared to implementing fastcgi on IIS in my
opinion. But anyway; follow the instructions here:
http://mapproxy.org/docs/latest/deployment.html#production on how to run
mapproxy on a fcgi-socket

From that point forward, I think you will be most likely to succeed by

implementing http://code.google.com/p/isapi-wsgi/ the fastCGI module you are
trying to use is pretty useless for sockets, especially python based...

This is true for the development server which is started via command line.
It includes a standalone http server which can be called from outside on
port 8080.
But for productional environments the mapproxy documentation recommends a
deployment via FastCGI. And why should I install another webserver which I
would have to secure seperately if I already have one.
-------- Original-Nachricht --------
Betreff: Re: [MapProxy] MapProxy 0.9 under IIS on Windows
Datum: 11/10/2010 11:58 AM

I am not completely sure, but in my opinion, mapproxy is a standalone
webserver acting on another port then port 80 (I believe it is 8080 by
default)
No need for modules or whatever on IIS.
So what you would need if you don't want visitors to enter the port
number like: http://someserver.org:8080/ you have to set up some port
forwarding mechanism from IIS

_______________________________________________
MapProxy mailing list
http://lists.osgeo.org/mailman/listinfo/mapproxy

--
Milo van der Linden
Open Source Geospatial consultant

do go digi - *Geospatial solutions*

Beukenlaan 2
5261LE Vught
[phone]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/mapproxy/attachments/20101110/c5e595e1/attachment.html

[Jörg Schräder]

No, my first reply was direct, yours was correct.

Post by Milo van der Linden
Securing the webserver is easy compared to implementing fastcgi on IIS
http://mapproxy.org/docs/latest/deployment.html#production on how to
run mapproxy on a fcgi-socket

I tried to do that but I did not succeed starting the socket. There is
an error message (after installing flup) saying "eunuchs module" is
missing when I try to start the server with the config.ini.

Post by Milo van der Linden
From that point forward, I think you will be most likely to succeed by
implementing http://code.google.com/p/isapi-wsgi/ the fastCGI module
you are trying to use is pretty useless for sockets, especially python
based...

This is interesting, I will have a deeper look into this! Thanks for the
advise! I will see If I get this running.

[Oliver Tonnhofer]

Hi J?rg, hi Milo,

the "included"[0] web server that runs when using the develop.ini is stable and works great for development or small installations, but it doesn't scale well with multiple cores.

CPU-bound Python applications do not benefit from multi-core CPUs when they run in threaded mode. You have to keep that in mind for you deployment strategy. See the small note at: http://mapproxy.org/docs/latest/deployment.html#other-deployment-options

[0] it's part of Paste, one of the MapProxy dependencies.

From that point forward, I think you will be most likely to succeed by implementing http://code.google.com/p/isapi-wsgi/ the fastCGI module you are trying to use is pretty useless for sockets, especially python based...

This is interesting, I will have a deeper look into this! Thanks for the advise! I will see If I get this running.

The options for windows are rather small, see:
http://stackoverflow.com/questions/4012621/python-wsgi-deployment-on-windows-for-cpu-bound-application


Regards,
Oliver