On 10/20/23 05:31, Wikinaut wrote:
The built-in template (mailman-hyperkitty.cfg) perhaps needs to be fixed as well (hyperkitty wrong, archive correct)? # However, if your Mailman installation is accessed via HTTPS, the URL needs # to match your SSL certificate (e.g. https://lists.example.com/hyperkitty). # base_url: http://localhost/mailman3/hyperkitty/
this line perhaps needs to be changed to # base_url: http://localhost/mailman3/archives/
I agree that this is confusing because some of our docs recommend that urls.py contain
path('postorius/', include('postorius.urls')),
path('hyperkitty/', include('hyperkitty.urls')),
and docs recommend
path('mailman3/', include('postorius.urls')),
path('archives/', include('hyperkitty.urls')),
I.e. following the first suggestion, you would access Postorius and
HyperKitty via https://www.example.com/postorius/ and
https://www.example.com/hyperkitty/ respectively, but with the second,
the urls would be https://www.example.com/mailman3/ and
https://www.example.com/archives/ respectively.
I'm going to address this by adding
path('postorius/', include('postorius.urls')),
path('hyperkitty/', include('hyperkitty.urls')),
to mailman_web's urls.py so the either urls will work. See https://gitlab.com/mailman/mailman-web/-/issues/24
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan