Code

Opened 6 years ago

Closed 5 years ago

Last modified 3 years ago

#9912 closed (fixed)

Docs: Adding info about other Webserver IPs than 127.0.0.1

Reported by: ed42 Owned by: jacob
Component: Documentation Version: 1.0
Severity: Keywords:
Cc: Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

This chapter:

http://docs.djangoproject.com/en/dev/intro/tutorial01/#the-development-server

.. should be complemented on how to allow access from other IPs than localhost (127.0.0.1).

As mentioned here:

http://forums.site5.com/showthread.php?p=139864

.. the python-webserver can be started with to allow access from non-localhost IPs:

python manage.py runserver 0.0.0.0:8000

Restriction to localhost makes sense from a security aspect, but prohibits access in virtual machine environments (like running python/django on a linux server that is hosted on Windows XP or OS/X via VMware).

This took me some time to figure out - a hint on 0.0.0.0:xxxx should help others to avoid the hassle.

Attachments (0)

Change History (6)

comment:1 Changed 6 years ago by ramiro

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset

Well, the tutorial is an introductory document, trying to describe there every possible usage variation would risk overwhelming the new user following it (such is the target audience) with so much information, a line should be drawn at some point.

There is alredy a "Changing the port" admonition note about how to change the port in which the development server listen that refers the reader to the runserver command reference documentation (http://docs.djangoproject.com/en/dev/ref/django-admin/#runserver-optional-port-number-or-ipaddr-port) where this is described.

comment:2 Changed 6 years ago by ed42

Having fixed the IP to 127.0.0.1 is all but trivial to assume.

This is more often a hurdle to getting the py-server run than the port question.

Instead of the lenghty "admonition note" a simple one line sentence would suffice.
Please consider again putting it there. EOT for me.

comment:3 Changed 5 years ago by jacob

  • milestone set to 1.1
  • Triage Stage changed from Unreviewed to Accepted

comment:4 Changed 5 years ago by jacob

  • Owner changed from nobody to jacob
  • Status changed from new to assigned

comment:5 Changed 5 years ago by jacob

  • Resolution set to fixed
  • Status changed from assigned to closed

(In [10371]) Fixed a whole bunch of small docs typos, errors, and ommissions.

Fixes #8358, #8396, #8724, #9043, #9128, #9247, #9267, #9267, #9375, #9409, #9414, #9416, #9446, #9454, #9464, #9503, #9518, #9533, #9657, #9658, #9683, #9733, #9771, #9835, #9836, #9837, #9897, #9906, #9912, #9945, #9986, #9992, #10055, #10084, #10091, #10145, #10245, #10257, #10309, #10358, #10359, #10424, #10426, #10508, #10531, #10551, #10635, #10637, #10656, #10658, #10690, #10699, #19528.

Thanks to all the respective authors of those tickets.

comment:18 Changed 3 years ago by jacob

  • milestone 1.1 deleted

Milestone 1.1 deleted

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.