1292ebb1bf
The wsgi_script feature is being removed because of some changes in underlying python packaging tooling. This makes heat to vendor the wsgi module which can be used instead of the wsgi script, according to the proposed community goal[1]. The existing wsgi scripts are kept now for smooth transition. [1] https://review.opendev.org/c/openstack/governance/+/902807 Depends-On: https://review.opendev.org/c/openstack/devstack/+/902758 Change-Id: I4dc92f06610753171215913180ce7cdab15ba047
23 lines
557 B
YAML
23 lines
557 B
YAML
---
|
|
features:
|
|
- |
|
|
A new module, ``heat.wsgi``, has been added as a place to gather WSGI
|
|
``application`` objects. This is intended to ease deployment by providing
|
|
a consistent location for these objects. For example, if using uWSGI then
|
|
instead of:
|
|
|
|
.. code-block:: ini
|
|
|
|
[uwsgi]
|
|
wsgi-file = /bin/heat-api
|
|
|
|
You can now use:
|
|
|
|
.. code-block:: ini
|
|
|
|
[uwsgi]
|
|
module = heat.wsgi.api:application
|
|
|
|
This also simplifies deployment with other WSGI servers that expect module
|
|
paths such as gunicorn.
|