I've had a similar thought that it would be nice to have some way to specify some default command arguments for management commands (such as --keepdb when running tests), however, adding settings (and/or environment variables?) for every such use case doesn't feel like it'll keep things simple.
I lean toward bash aliases to meet these needs, although moving the hardcoded '127.0.0.1' in runserver so it can be more easily overridden is certainly fine. On Thursday, December 8, 2016 at 6:50:53 AM UTC-5, Kamal Velan wrote: > > Considering how the secret key is still in the settings.py giving the user > the option to make it an env variable > this can follow the same suit. > > On Monday, 28 November 2016 21:15:17 UTC+5:30, Florian Apolloner wrote: >> >> -1 on a setting for that. I'd be okay with a DJANGO_RUNSERVER_BINDHOST >> environment variable or similar. >> >> On Monday, November 28, 2016 at 3:10:06 PM UTC+1, is_null wrote: >>> >>> Perhaps we could override this default with a setting ? >>> >> -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/b705c0e8-ddce-4163-8c3c-2a25c3e3b68d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
