combine postorius and hyperkitty into one Apache vhost
Hi,
I'm in the process to set up a new mailman3 site. (Migrating from mailman2)
There are RPMs for my distribution which integrate postorius and hyperkitty with uwsgi.
The provided samples assume that both are running in different vhosts what I would like to avoid.
Since I couldn't find any uwsgi examples for that I'm experimenting heavily but still having issues. I might just miss a simple thing (hopefully).
My current apache config: Alias "/mailman/static" "/srv/www/webapps/mailman/postorius/static" ProxyPassMatch ^/mailman/static ! ProxyPass /mailman unix:/run/uwsgi/uwsgi-postorius.sock|uwsgi://localhost-postorius/
Alias "/archives/static" "/srv/www/webapps/mailman/hyperkitty/static"
ProxyPassMatch ^/archives/static !
ProxyPass /archives unix:/run/uwsgi/uwsgi-hyperkitty.sock|uwsgi://localhost-hyperkitty/
This currently assumes that postorius just gets a mailman/ prefix and hyperkitty archives/
This setup immediately fails because of the urlpatterns filter in these components. For testing purposes I changed the patterns in urls.py slightly and I could make it work for me.
BUT: This cannot be the solution, can it? Isn't there an easier way to allow these components to run under a different document root?
Something slightly unrelated but causing issues in some edge cases also is that Django? does not detect the request url properly.
For some functionality e.g. when I want to login to Django admin under /archives/admin (even after modifying urls.py) I get a redirect after the form which shows that my initial path was not recognized as /archives/admin but /archive//admin instead. So the last character is replaced with a /
Any hints for me?
Thanks, Wolfgang
On 12/29/22 05:51, Wolfgang Rosenauer wrote:
Hi,
I'm in the process to set up a new mailman3 site. (Migrating from mailman2)
There are RPMs for my distribution which integrate postorius and hyperkitty with uwsgi.
I think you'll be much happier if you don't use the distro's RPMs which are probably out of date and instead follow <https://docs.mailman3.org/en/latest/install/virtualenv.html>. Those instructions use uWSGI as a WSGI interface, but Gunicorn <https://gunicorn.org/> is what is used on the site supporting this list. The advantages of Gunicorn are it's already installed as a dependency of Mailman core, and it's what the Mailman developers are more familiar with.
I'll work on updating <https://docs.mailman3.org/en/latest/install/virtualenv.html> to include Gunicorn as an alternative.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
So you prefer Gunicorn over uWSGI? When I have a working installation that uses uwsgi, should I reconfigure for Gunicorn? At the moment I see no reason for this, and while I am open for alternate solutions, ... ยด never change a running system
Am Donnerstag, 29. Dezember 2022, 21:48:54 CET schrieb Mark Sapiro:
On 12/29/22 05:51, Wolfgang Rosenauer wrote:
Hi,
I'm in the process to set up a new mailman3 site. (Migrating from mailman2)
There are RPMs for my distribution which integrate postorius and hyperkitty with uwsgi.
I think you'll be much happier if you don't use the distro's RPMs which are probably out of date and instead follow <https://docs.mailman3.org/en/latest/install/virtualenv.html>. Those instructions use uWSGI as a WSGI interface, but Gunicorn <https://gunicorn.org/> is what is used on the site supporting this list. The advantages of Gunicorn are it's already installed as a dependency of Mailman core, and it's what the Mailman developers are more familiar with.
I'll work on updating <https://docs.mailman3.org/en/latest/install/virtualenv.html> to include Gunicorn as an alternative.
On 12/29/22 12:58, Eggert Ehmke via Mailman-users wrote:
So you prefer Gunicorn over uWSGI? When I have a working installation that uses uwsgi, should I reconfigure for Gunicorn? At the moment I see no reason for this, and while I am open for alternate solutions, ...
No, don't change. If uWSGI is working for you, it's fine. I prefer Gunicorn and recommend it for new installations because it's already installed as a dependency of Mailman core, at least if the web UI is on the same machine as Mailman core, and because I think its configuration is simpler than uWSGI.
uWSGI does have an advantage in that it can be configured to start qcluster eliminating the need to do that separately.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (3)
-
Eggert Ehmke -
Mark Sapiro -
Wolfgang Rosenauer