Issue #910
closedPulp's use of Django is not production ready
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.
Updated by dkliban@redhat.com over 9 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to dkliban@redhat.com
Updated by dkliban@redhat.com over 9 years ago
- Status changed from ASSIGNED to POST
Added by dkliban@redhat.com over 9 years ago
Added by dkliban@redhat.com over 9 years ago
Revision ff59e52f | View on GitHub
Turned off DEBUG in django settings.py
Fixes #910
Updated by dkliban@redhat.com over 9 years ago
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
Applied in changeset pulp|ff59e52f6f75ab9b798bdaad59c8c0298c4ef5d5.
Updated by dkliban@redhat.com about 9 years ago
- Status changed from MODIFIED to 5
Updated by amacdona@redhat.com almost 9 years ago
- Status changed from 5 to CLOSED - CURRENTRELEASE
Turned off DEBUG in django settings.py
Fixes #910