Django 1.4 stopped creating django.wsgi files and the common
practice now for a while has been a wsgi.py since it is actually
python code, and should actually be importable.
Right now someone has to copy and rename the existing file if they
want to use it with a server like gunicorn.
This patch adds a new file in location that is importable via python
and adds a deprecation log to the old one.
This also updates the wsgi generation commands to instead create
'horizon_wsgi.py' and have the apache conf generation also use that
or the default wsgi file.
Reviewed: https:/ /review. openstack. org/561802 /git.openstack. org/cgit/ openstack/ horizon/ commit/ ?id=0ca736e5da4 7413db6749053e6 083b82cbb24825
Committed: https:/
Submitter: Zuul
Branch: master
commit 0ca736e5da47413 db6749053e6083b 82cbb24825
Author: Adrian Turjak <email address hidden>
Date: Tue Apr 17 18:27:27 2018 +1200
Create new wsgi.py file and deprecate old file
Django 1.4 stopped creating django.wsgi files and the common
practice now for a while has been a wsgi.py since it is actually
python code, and should actually be importable.
Right now someone has to copy and rename the existing file if they
want to use it with a server like gunicorn.
This patch adds a new file in location that is importable via python
and adds a deprecation log to the old one.
This also updates the wsgi generation commands to instead create wsgi.py' and have the apache conf generation also use that
'horizon_
or the default wsgi file.
Change-Id: I0f8bd16c8973ad 23bcd8f73b54584 dc69e5aed0c
Closes-Bug: #1763204