> >
> > 2. setting the ROOT_URLCONF = 'urls2' in the /etc/mailman3/mailman-web.py
> >
> > or /usr/share/mailman3-web/settings.py
> > and adding a link in /usr/share/mailman3-web/urls2.py to
> > file /etc/mailman3/mailman-web.urls2.py
> >
> > containing:
> > ======
> > from django.conf.urls import include, url
> > from django.contrib import admin
> > from django.core.urlresolvers import reverse_lazy
> > from django.views.generic import RedirectView
> >
> > urlpatterns = [
> >
> > url(r'^<additional-base-url>', include('urls')),
> >
> > ]
> > =====
> >
>
> Can you give me a little more intel on what you'd like to achieve by
> modifying/allowing modifications of the urls set of the application?
>
> Mind that adding such feature means allowing the shared memory of the django
> app to be accessed by non-upstream code. Should a user badly implement
> features, this could possibly compromise all his mailman3 setup. I'm not
> sure it's a sane thing to do, but I'm not opposed to it either.
>
> So, let's discuss, think, and we'll try to find an appropriate solution that
> pleases anyone but does not compromise the app stability.
I just don't want to expose mailman on the default URL, similar as
other sites like
https://mail.python.org/mm3/mailman3/lists/distutils-sig.python.org/ do.
If there is an other simple method to achieve this I'm happy too.
Thank you for you question!
Cheers!
