tags 903104 +moreinfo
thanks
Le vendredi 06 juillet 2018 à 09:39:16+0200, bgr...@toplitzer.net a écrit :
> Package: mailman3-web
> Version: 0+20170523-14~bpo9+1
> Severity: wishlist
>
> Currently configuration of the base URL is not possible without
>
> 1. modifying /usr/share/mailman3-web/urls.py (regular package-file)
>
> or
>
> 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')),
> ]
> =====
>
> or
>
> 3. same as 2 with ROOT_URLCONF = 'package.url...' and separate package.
>
> Please include method 2 into the package with
> descriptive template.Hi, Thanks for submitting your bug. :) 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. Cheers! -- Pierre-Elliott Bécue GPG: 9AE0 4D98 6400 E3B6 7528 F493 0D44 2664 1949 74E2 It's far easier to fight for one's principles than to live up to them.
signature.asc
Description: PGP signature
