On 6/9/19 3:18 AM, andrew.bernard@gmail.com wrote:

Using the Ubuntu 19 packages for all the mailman suite, uwsgi is the Python WSGI server included. I have now switched over to a full build from current source from gitlab, following Mark Sapiro's excellent instructions.

Thank you.

It would appear that the current code has the use of gunicorn built in. Is gunicorn the preferred way now to run the mailman Django apps? Is it worth spending time converting everything to use uwsgi, or should I go with the flow and use gunicorn?

The "built-in" gunicorn is used only by core to provide the REST API interface. This replaced the former standard library wsgiref module to improve performance. It is completely independent of whatever WSGI server you use for Django.

What are the advantages of gunicorn over uwsgi?

I can't comment intelligently on that. For a long time I used Graham Dumpleton's mod_wsgi with Apache for wsgi support, mostly for MoinMoin. I have no experience with uwsgi.

When I set up MM 3 on lists.mailman3.org, the server was already using nginx so I arbitrarily chose gunicorn for that. On mail.python.org I started using mod_wsgi, but at one point there was an issue due apparently to an SSL library mismatch following an upgrade, but before the cause was recognized, I switched to gunicorn to get things up.

On a third server I manage, I use mod_wsgi for MoinMoin which is Python 2.7. I found setting up both Python 2.7 and Python 3 versions of mod_wsgi on the same server to be daunting, so I went with gunicorn for Mailman 3 on that server too.

My choices of gunicorn over uwsgi were an initial arbitrary choice followed by familiarity for subsequent choices.

-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan