[MapProxy] Best way to deploy mapproxy

[Daniel Araujo Miranda]

Thanks, that helped me too.
--Miranda

On 07/20/2012 04:13 AM, Oliver Tonnhofer wrote:
> Hi Benjamin,
>
> On 19.07.2012, at 23:00, Benjamin Wragg wrote:
>> So far I've just been running it as serve-develop but I'm getting close to putting it into the production environment. I've looked at the ways it can be deploy and I'm a little overwhelmed with all the available options. Just wondered if anyone has any comments on which deployment method and software options is the fastest/best/preferred?
>
> There are a lot of option and the documentation does not really help to choose the right one. I should put that bit higher on my todo list.
>
>> 2) FastCGI behind HTTP server (flup, apache, nginx, lighttpd)
>
> We don't recommend this setup anymore. There is only one Python implementation of FastCGI (flup) and that one is no longer maintained (last stable release is from 2009). In theory it should be faster that the HTTP/HTTP-PRoxy solution, but the competition between the multiple HTTP implementations pushed them farther than FastCGI.
>
>> 3) Embedded in HTTP server (apache and others)
>
> This one is the easiest to setup, especially if you are already familiar with Apache. Make sure you are using WSGIDaemonProcess/WSGIProcessGroup and that you setup WSGIPythonHome if you use virtualenv.
> mod_wsgi is actively maintained and the performance is good enough for almost all setups.
>
>> 1) HTTP behind HTTP Proxy (Gunicorn, Spawning, Nginx, Apache)
>
> We use Gunicorn with eventlet and Ngxin for most of our setups. This setup is also well maintained, but of course you need to be familiar with Nginx (which we are). This setup has a slight advantage for tiles services with lots of requests.
>
>
>> I'm running Ubuntu 12 server. Its just going to run on an internal ethernet network, not over the web. I have no real preference on the web server so I'm open to suggestion. I've used Apache previously for other apps but if something is faster I'd love to hear about it.
>
>
> Then try Apache first.
>
>
> Regards,
> Oliver
>