Re: [galaxy-dev] Galaxy, Apache, WSGI and mod_wsgi

2012-10-24 Thread Carl Eberhard
Hi, Paul I would like to know if mod_wsgi has been considered for the deployment of Galaxy at all, and whether anyone has any positive or negative experiences with it. I can only speak for the second part of your question: I've had some experience with Apache 2 + mod_wsgi, but within a Django

Re: [galaxy-dev] Galaxy, Apache, WSGI and mod_wsgi

2012-10-24 Thread Paul Boddie
On 24/10/12 18:09, Carl Eberhard wrote: I would like to know if mod_wsgi has been considered for the deployment of Galaxy at all, and whether anyone has any positive or negative experiences with it. I can only speak for the second part of your question: I've had some experience with Apache 2

Re: [galaxy-dev] Galaxy, Apache, WSGI and mod_wsgi

2012-10-24 Thread James Taylor
The Galaxy application does store quite a bit in memory (not as globals though). This doesn't preclude running under mod_wsgi, but it will work best in a configuration that uses a small number of long running processes with multiple threads. Basically, we run nginx proxying paste on the main

[galaxy-dev] Galaxy, Apache, WSGI and mod_wsgi

2012-10-22 Thread Paul Boddie
Hello, I have recently had the opportunity to look at the deployment of Galaxy together with Apache, and I saw that the recommendation is to run the Galaxy Web server behind Apache with the latter acting as a proxy: http://wiki.g2.bx.psu.edu/Admin/Config/Apache%20Proxy Other than