Issue #910: Pulp's use of Django is not production ready - Pulp

Actions

Send by e-mail Copy link

Issue #910

closed

Pulp's use of Django is not production ready

Added by bmbouter over 9 years ago. Updated over 5 years ago.

Status:

CLOSED - CURRENTRELEASE

Priority:

High

Assignee:

dkliban@redhat.com

Category:

Sprint/Milestone:

Start date:

Due date:

Estimated time:

Severity:

2. Medium

Version:

Platform Release:

2.7.0

OS:

Triaged:

Yes

Groomed:

Sprint Candidate:

Tags:

Pulp 2

Sprint:

Quarter:

Description

As we prepare to release Pulp's Django code, it needs to be touched up so that it is production ready.

In the settings.py file that Pulp sets DEBUG and TEMPLATE_DEBUG to True. This was helpful early on while porting Django, but now that the port is stable and to be released with Pulp 2.7.0 we should set these both to False.

Once these are disabled we will also need to update the ALLOWED_HOSTS setting which is bypassed while DEBUG=True. We set that setting here.

Finally the SECRET_KEY does not need to be kept secret in production or development so the scary warning above it needs to be removed.

These changes need to be sanity checked against the different version of Django for EL6, EL7, and FC21. You can install the desired version for testing using pip.