Re: Provide a simpler way to default runserver IP/port to 0.0.0.0:8000

Mario, It's not the best to re-open a 2.5 year old thread :) Better to start a new one, link to the old one, and state what you think is different. I believe your use case can be fit with a custom ruserver management command to override the original as Shai suggested: > from (...)runserver

Re: Provide a simpler way to default runserver IP/port to 0.0.0.0:8000

was this rejected? my use case is: I have a single django program, which I run in multiple instances, each on a different port and connecting to a different database. for each instance, I have a separate `config_INSTANCE.py` file. the database settings fit in the `config` file, but I have to

Re: Provide a simpler way to default runserver IP/port to 0.0.0.0:8000

I am -1 on adding a setting to handle a use-case that can be handled by users with a 6-line file: On Monday 28 November 2016 16:05:39 Shai Berger wrote: > > It seems all you need in the overridden runserver is: > > from (...)runserver import Command as BaseCommand > > class

Re: Provide a simpler way to default runserver IP/port to 0.0.0.0:8000

I'd find this really helpful right now. Solution 1, overriding the default in a settings file is the easiest solution to understand and the fastest to set up, against 2 and 3 standalone. Solution 2 comes for free with Solution 1 - a user can read from environment variables via settings files

Re: Provide a simpler way to default runserver IP/port to 0.0.0.0:8000

If it helps, there's a also a shortcut: ./manage.py runserver 0:8000. Much easier to type. On Mon, Nov 28, 2016 at 8:48 AM, wrote: > This was filed as https://code.djangoproject.com/ticket/27537 , but > moving here for discussion. > > We have the following use case: > * An

Re: Provide a simpler way to default runserver IP/port to 0.0.0.0:8000

What exactly would that achieve or do? Also what does PACKAGE in that context mean? Django has projects and apps and a simple settings.py file. Are you proposing to add a new file where apps could declare settings? How would those be merged, etc… Cheers, Florian On Thursday, December 8, 2016

Re: Provide a simpler way to default runserver IP/port to 0.0.0.0:8000

On Thursday, December 8, 2016 at 8:16:02 AM UTC-8, Florian Apolloner wrote: > > On Thursday, December 8, 2016 at 5:04:46 PM UTC+1, Zach wrote: >> >> How about a PACKAGE setting similar to npm's package.json >> . >> > > Seems to be yet another way to do

Re: Provide a simpler way to default runserver IP/port to 0.0.0.0:8000

On Thursday, December 8, 2016 at 5:04:46 PM UTC+1, Zach wrote: > > How about a PACKAGE setting similar to npm's package.json > . > Seems to be yet another way to do what custom management commands already over (with less overhead for sure, but also

Re: Provide a simpler way to default runserver IP/port to 0.0.0.0:8000

How about a PACKAGE setting similar to npm's package.json . PACKAGE = { 'scripts': { 'test': 'test --keepdb', 'runserver': 'runserver --ipv6', }, } On Thursday, December 8, 2016 at 6:32:19 AM UTC-8, Tim Graham wrote: > > I've

Re: Provide a simpler way to default runserver IP/port to 0.0.0.0:8000

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

Re: Provide a simpler way to default runserver IP/port to 0.0.0.0:8000

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 >

Re: Provide a simpler way to default runserver IP/port to 0.0.0.0:8000

I recon i use a single settings module that feeds from env vars for any project i touch myself, but I suggested adding a setting because that would leave the choice up to the user like it's currently the case in django projects (some people still rely on local_settings import or use several

Re: Provide a simpler way to default runserver IP/port to 0.0.0.0:8000

-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

Re: Provide a simpler way to default runserver IP/port to 0.0.0.0:8000

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

Re: Provide a simpler way to default runserver IP/port to 0.0.0.0:8000

On Monday 28 November 2016 15:48:21 emor...@mozilla.com wrote: > This was filed as https://code.djangoproject.com/ticket/27537 , but moving > here for discussion. > It seems all you need in the overridden runserver is: from (...)runserver import Command as BaseCommand class

Provide a simpler way to default runserver IP/port to 0.0.0.0:8000

This was filed as https://code.djangoproject.com/ticket/27537 , but moving here for discussion. We have the following use case: * An app uses a VM for the local development environment (eg via Vagrant). * It's required to be accessible from the VM host (either on it's own IP, or on localhost