[PATCH] django-admin.py runserver only takes a port when it could also take an ip:port

[benno@…]

Currently django-admin.py's runserver command can only take a port number and will always use 127.0.0.1 as the bind address. This patch allows an IP address to be specified by passing <ip address>:<port> instead of just <port>.

[benno@…]

Patch to add ip:port as well as port argument to runserver.

[benno@…]

Fixed version (fixes up empty addr string)

[Adrian Holovaty]

Thanks for this patch.

Before we roll it in, I have a question: What's the use-case for this? Why would somebody need to run the development server (which should NOT be run on a production site) on a separate IP address?

[Simon Willison]

Here's a use case: you are running the development server on a machine which has a public internet facing IP address and another address that is only visible to your network. You would want the development server to face internally only. This isn't that unlikely in a small development shop where the dev box might double up as the office router.

[Adrian Holovaty]

(In [539]) Fixed #360 -- runserver now takes optional 'ip:port' in addition to 'port'. Thanks, benno@…

[fonso]

In my case, this patch makes the the server refuse remote connections if I don't explicitly indicate the public interface IP. E.g., I have to use:

$ django-admin.py runserver 192.168.1.4:8000

Changing line 550 in core/management.py (​http://code.djangoproject.com/file/django/trunk/django/core/management.py?rev=539) to just addr = '' fixes this.

[fonso]

Don't explicitly specify the binding address for the server

[fonso]

Don't explicitly specify the binding address for the server (second try)

[rff_rff@…]

another use case: I'm developing on a virtual machine with a minimal installation and connecting from my real one to test. I applied the same change as in dj360_539.2.diff by myself, because it is so much easier to work that way.