docs: document the example Gunicorn conf file

Update the Admin Guide for two nodes to reflect that since v0.14.8
Synnefo ships an example configuration file for Gunicorn automatically
installed at '/etc/gunicorn.d/synnefo.example'.

Also, update the upgrade guide and changelog accordingly.
parent 4cba4c56
......@@ -20,7 +20,8 @@ Synnefo-wide
can mix and match nodes freely.
* Update Django dependency to Django>=1.2,<1.5. Django 1.4.5 is available for
Squeeze through squeeze-backports.
* Since this version, Synnefo ships an example Gunicorn configuration file
that is automatically installed at ``/etc/gunicorn.d/synnefo.example``.
Cyclades
--------
......
......@@ -1813,6 +1813,7 @@ Upgrade Notes
v0.13 -> v0.14 <upgrade/upgrade-0.14>
v0.14 -> v0.14.2 <upgrade/upgrade-0.14.2>
v0.14.5 -> v0.14.6 <upgrade/upgrade-0.14.6>
v0.14.7 -> v0.14.8 <upgrade/upgrade-0.14.8>
Changelog, NEWS
......
......@@ -202,25 +202,13 @@ actual IPs. Now, restart the server to apply the changes:
Gunicorn setup
~~~~~~~~~~~~~~
Create the file ``/etc/gunicorn.d/synnefo`` containing the following:
Rename the file ``/etc/gunicorn.d/synnefo.example`` to
``/etc/gunicorn.d/synnefo``, to make it a valid gunicorn configuration file:
.. code-block:: console
CONFIG = {
'mode': 'django',
'environment': {
'DJANGO_SETTINGS_MODULE': 'synnefo.settings',
},
'working_dir': '/etc/synnefo',
'user': 'www-data',
'group': 'www-data',
'args': (
'--bind=127.0.0.1:8080',
'--worker-class=gevent',
'--workers=8',
'--log-level=debug',
),
}
# mv /etc/gunicorn.d/synnefo.example /etc/gunicorn.d/synnefo
.. warning:: Do NOT start the server yet, because it won't find the
``synnefo.settings`` module. Also, in case you are using ``/etc/hosts``
......@@ -388,27 +376,14 @@ of the purpose of this guide.
Gunicorn setup
~~~~~~~~~~~~~~
Create the file ``/etc/gunicorn.d/synnefo`` containing the following
(same contents as in node1; you can just copy/paste the file):
Rename the file ``/etc/gunicorn.d/synnefo.example`` to
``/etc/gunicorn.d/synnefo``, to make it a valid gunicorn configuration file
(as happened for node1):
.. code-block:: console
CONFIG = {
'mode': 'django',
'environment': {
'DJANGO_SETTINGS_MODULE': 'synnefo.settings',
},
'working_dir': '/etc/synnefo',
'user': 'www-data',
'group': 'www-data',
'args': (
'--bind=127.0.0.1:8080',
'--worker-class=gevent',
'--workers=4',
'--log-level=debug',
'--timeout=43200'
),
}
# mv /etc/gunicorn.d/synnefo.example /etc/gunicorn.d/synnefo
.. warning:: Do NOT start the server yet, because it won't find the
``synnefo.settings`` module. Also, in case you are using ``/etc/hosts``
......
Upgrade to Synnefo v0.14.8
^^^^^^^^^^^^^^^^^^^^^^^^^^
Since v0.14.8, Synnefo ships an example Gunicorn configuration file, that gets
installed automatically at ``/etc/gunicorn.d/synnefo.example``.
To use it you need to do two things:
1. Disable your old configuration file by removing it.
[if you are upgrading from an older version and you had such a file]
2. Rename the file to ``/etc/gunicorn.d/synnefo`` to make it valid:
.. code-block:: console
# mv /etc/gunicorn.d/synnefo.example /etc/gunicorn.d/synnefo
Finally, add any other special configuration option needed by your deployment in
this file.
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment