On 6/26/23 1:15 AM, Odhiambo Washington wrote:
On Mon, Jun 26, 2023 at 9:29 AM Stephen J. Turnbull < turnbull.stephen.fw@u.tsukuba.ac.jp> wrote:
Yes, it makes sense. Mailman 3 core is basically an application which manages a webserver that provides the REST API, a database of domains, users, and lists, an LMTP server for incoming posts and an SMTP client for outgoing distribution. Mailman uses gunicorn to provide the webserver.
Installation of gunicorn is handled as a package dependency, so you probably wouldn't notice unless you were watching the installation process very carefully.
It doesn't make sense, IMHO, because as the OP says,
his ExecStart is: ExecStart=/opt/mailman/venv/bin/uwsgi --ini /etc/mailman3/uwsgi.ini" *and not* ExecStart=/opt/mailman/venv/bin/gunicorn -c /etc/mailman3/gunicorn.conf mailman_web.wsgi:application.
He has not knowingly created any gunicorn.conf
Why would Gunicorn be Exec-ing itself? :-)
As Steve says, Mailman core uses Gunicorn to manage it's REST API. This has nothing to do with whatever WSGI server (uWSGI, Gunicorn, Apache mod_wsgi, ...) is used to support the Django applications (django-mailman3, hyperkitty and postorius).
I.e., there is always a Gunicorn instance configured and started by Mailman core, regardless of whatever WSGI server supports Django or even if one isn't running Django at all.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan