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 stack. There was a somewhat complex set up/configuration (not horrible, just tedious) - that may have been particular to our situation and/or Django. It might be easier in your Galaxy situation. After set up, I found it pretty easy to work with: - Very rarely had to deal with bugs/workarounds or modification in general. - His/Their documentation for the mod is excellent - which is an often understated positive. - I found no problems with logging, debugging, or the mod 'getting in the way' of normal Apache features. - If I recall correctly, there was a good user base out there (~2-3 years ago). Carl On Mon, Oct 22, 2012 at 9:26 AM, Paul Boddie <paul.bod...@biotek.uio.no>wrote: > 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<http://wiki.g2.bx.psu.edu/Admin/Config/Apache%20Proxy> > > Other than convenience - one can just put Apache in front of an existing > server - is there any particular reason for doing things this way? It seems > that Galaxy uses the built-in Web server provided by the Paste framework, > which in turn is based on the Python standard library BaseHTTPServer > framework, and although paste.httpserver seems to add capabilities to the > underlying framework, each such server must still be constrained to running > in a single process. I imagine that this then leads to the use of load > balancing as described on the following page: > > http://wiki.g2.bx.psu.edu/**Admin/Config/Performance/Web%** > 20Application%20Scaling<http://wiki.g2.bx.psu.edu/Admin/Config/Performance/Web%20Application%20Scaling> > > Given that Apache is an acceptable part of a large-scale solution, 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. It seems to me that mod_rewrite is often something that should only be > brought into play where other, typically more elegant, solutions cannot be > used. Many Python-based Web applications have mod_wsgi as a recommended > deployment option once their users look beyond CGI, and I wondered why this > isn't the case with Galaxy. > > Paul > ______________________________**_____________________________ > Please keep all replies on the list by using "reply all" > in your mail client. To manage your subscriptions to this > and other Galaxy lists, please use the interface at: > > http://lists.bx.psu.edu/ >
___________________________________________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/