Hi Tobias, On Sunday, October 30, 2022 at 2:02:36 AM UTC+2 tob...@caktusgroup.com wrote:
> Regarding DJANGO_ENV, why not ship the template with two settings files > and use the existing DJANGO_SETTINGS_MODULE, instead of adding a new > environment variable? > That is certainly one way to do it and probably the most controversial point. Ie what does DJANGO_ENV=dev|staging|prod offer over `DJANGO_SETTINGS_MODULE=your_project.settings.dev|staging|prod` Maybe that would be controversial too, I'm not sure, but perhaps less so > than introducing a new paradigm? In any event, perhaps a pluggable backend > would allow everyone to be happy, or very nearly so... š > If we can come up with a reasonable API :) I wonder if a setuptools entrypoint to automatically enable your backend solely by installing it alongside the product would be one way to allow for easy customizationā¦ We might need two things to get this all started: An documented API contract that we can discuss and also a set of usecases that we do want to allow? Cheers, Florian -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/1e0a0540-fcfa-45b0-bedc-f213aab9b267n%40googlegroups.com.
