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