[MM3-users] Re: mm3 installation question

Odhiambo Washington writes:

Mark Sapiro writes:

...

Some of the path settings are probably not in the same order as in that file. The

     path('mailman3/', include('postorius.urls')),
     path('archives/', include('hyperkitty.urls')),

settings should come after the

     path('postorius/', include('postorius.urls')),
     path('hyperkitty/', include('hyperkitty.urls')),

settings (unfortunately, mailman-web 0.0.8 has these in the wrong order). Or you can just delete the 'postorius/' and 'hyperkitty/' ones or you can add

     ProxyPass "/postorius" "http://127.0.0.1:8000/postorius"
     ProxyPass "/hyperkitty" "http://127.0.0.1:8000/hyperkitty"

to your Apache config.

The odd thing is that the HOWTO that he followed never involves the manipulation of any urls.py at all - it's not even mentioned at any point. So obviously the issue is caused by something else and I suspect something within Apache needs to be re-evaluated in the guide.

I believe this is the Apache configuration the OP is using:

<IfModule mod_proxy.c>
    ProxyPreserveHost On
    ProxyPass "/mailman3" "http://127.0.0.1:8000/mailman3"
    ProxyPass "/archives" "http://127.0.0.1:8000/archives"
    ProxyPass "/accounts" "http://127.0.0.1:8000/accounts"
    ProxyPass "/admin" "http://127.0.0.1:8000/admin"
    ProxyPass "/user-profile" "http://127.0.0.1:8000/user-profile"
</IfModule>

Note that Apache doesn't know about the "/postorius" and "/hyperkitty" URI paths. It is quite unclear to me how this works at all with either the

path('mailman3/', include('postorius.urls')),
path('archives/', include('hyperkitty.urls')),
path('postorius/', include('postorius.urls')),
path('hyperkitty/', include('hyperkitty.urls')),

version of urls.py or the reverse order version

path('postorius/', include('postorius.urls')),
path('hyperkitty/', include('hyperkitty.urls')),
path('mailman3/', include('postorius.urls')),
path('archives/', include('hyperkitty.urls')),

I think Mark must have a configuration with

ProxyPass "/" "http://127.0.0.1:8000/"

in the Apache configuration in mind? Or an alias or rewrite rule. Otherwise I don't see how "/postorius" and "/hyperkitty" paths ever get transmitted to the WSGI server.

Steve