wow , i faced the [ static and preload problem ] of settings.py once .. you cant govl around it becouse its how they designed django , you cant even pass empty containers for any future values , or will be calculated from the very next script after settings.py , you cant do that , there is no such a lazy load in settings.py so dont try this way , think of another way or you have to mess with django source code ..
one hack around is to load all the plugins once you create the project , but make them hidden or unaccessible untill the user want a certain option-plugin so you make it visible for him On Mon, 30 Jul 2018, 07:36 Melvyn Sopacua, <m.r.sopa...@gmail.com> wrote: > On zondag 29 juli 2018 23:14:34 CEST Christian González wrote: > > On zondag 29 juli 2018 11:02:30 CEST Christian González wrote: > > > > There might also be another reason and that is that in the Python > > > community, there's a good realisation that downloadable and instantly > > > installable plugins for a web project without dev(ops) interference > > > isn't necessarily a good thing. > > > > Mh, not really. Look at Owncloud/Nextcloud. Is PHP, but a good example > > that this works. > > I have a good amount of experience with Magento, which has the same > principle > and dealt with all the downsides of it. But I personally don't know of any > similar project within the Python community. > > Doesn't mean it doesn't exist, just not as wide spread and after having > dealt > with the security holes, low quality not performing code, layout breakers > and > what not - I can't say I'm surprised. Magento has invested quite a bit in > ways > to check code quality on everything that hits the store. > > Either way, keep in mind that you're not going to solve this *just* at the > Django layer. You'll need some way to trigger the WSGI processor to load > the > new code in a safe manner and then run migrations. Good luck! > > -- > Melvyn Sopacua > > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-users+unsubscr...@googlegroups.com. > To post to this group, send email to django-users@googlegroups.com. > Visit this group at https://groups.google.com/group/django-users. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-users/1637102.li6HjgoyNo%40fritzbook > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAHV4E-fzyNP7gsLtZgYSWwX%2BeUxG3QKK7eaN0Kq6Q2UK0O9tbA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
