45👍
I think the OP is referring to having multiple interfaces configured on the test machine.
You can specify the IP address that Django will bind to as follows:
# python manage.py runserver 0.0.0.0:8000
This would bind Django to all interfaces on port 8000. You can pass any active IP address in place of 0.0.0.0, so simply use the IP address of the interface you want to bind to.
Hope this helps.
2👍
Yes, if the IP of your interface is for example 192.168.1.2 and you want to run on port 8080, start the development server like this:
./manage.py runserver 192.168.1.2:8080
- Django order items by two fields, but ignoring them if they're zero
- Django vs. Pylons
- Store browser tab specific data
- Django app in heroku getting worker timeout error
- Installing django 1.5(development version) in virtualenv
1👍
No. It’s not how it works. The interface has an IP address, you have a network with the test server and your PC. You should connect to that IP (possibly with an alternative port that you specified), and that’s all. If you only have these two devices in the network, it is most likely that both of them should have static IP addresses. (or, if there is not mutual network, you cannot connect to each other).
- Django: why are Django model fields class attributes?
- Django Views: When is request.data a dict vs a QueryDict?
- Pycharm Django Debugging is really slow
- Django HTML E-mail template doesn't load css in the e-mail