Code

Opened 8 years ago

Closed 8 years ago

Last modified 8 years ago

#1638 closed enhancement (fixed)

Specific shortcomings of development server should be documented

Reported by: pb@… Owned by: jacob
Component: Documentation Version:
Severity: normal Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

The docs do a good job of admonishing the user not to rely on the development server in a production environment, but are thin on technical specifics.

References:

http://www.djangoproject.com/documentation/django_admin/#runserver-optional-port-number-or-ipaddr-port
http://www.djangoproject.com/documentation/faq/#do-i-have-to-use-mod-python
http://www.djangoproject.com/documentation/tutorial1/#the-development-server
http://www.djangoproject.com/documentation/static_files/#the-big-fat-disclaimer

Only the last of those four ventures to give a reason for the prohibitions. I'm sure other reasons exist, but it would be nice if there were a place in the docs (which the above passages could reference) where they were explained. I don't think a huge amount of technical detail is needed, but "just don't do that" isn't quite enough.

Attachments (0)

Change History (1)

comment:1 Changed 8 years ago by adrian

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

(In [3062]) Fixed #1638 -- Documented shortcomings of development server in docs/django-admin.txt

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.