| 1 |
--- |
| 2 |
features: |
| 3 |
- | |
| 4 |
A new module, ``blazar.wsgi``, has been added as a place to gather WSGI |
| 5 |
``application`` objects. This is intended to ease deployment by providing a |
| 6 |
consistent location for these objects. For example, if using uWSGI then |
| 7 |
instead of: |
| 8 |
|
| 9 |
.. code-block:: ini |
| 10 |
|
| 11 |
[uwsgi] |
| 12 |
wsgi-file = /bin/blazar-api-wsgi |
| 13 |
|
| 14 |
You can now use: |
| 15 |
|
| 16 |
.. code-block:: ini |
| 17 |
|
| 18 |
[uwsgi] |
| 19 |
module = blazar.wsgi.api:application |
| 20 |
|
| 21 |
This also simplifies deployment with other WSGI servers that expect module |
| 22 |
paths such as gunicorn. |
| 23 |
upgrade: |
| 24 |
- | |
| 25 |
The WSGI script ``blazar-api-wsgi`` has been removed. Deployment tooling |
| 26 |
should instead reference the Python module path for the wsgi module in |
| 27 |
Blazar, ``blazar.wsgi.api:application`` if their chosen WSGI server |
| 28 |
supports this (gunicorn, uWSGI, etc.) or implement a .wsgi script |
| 29 |
themselves if not (mod_wsgi). |