[sec-guide] Consistent the 'Nginx' term

This patch should be merged after this commit
https://review.openstack.org/#/c/366445/

Change-Id: Ia81495ccc52464672c77d942654aa084ce0cc7c7
Partial-Bug: #1619491
This commit is contained in:
chenxing 2016-07-22 03:21:58 +08:00 committed by chen.xing
parent eece60f5fc
commit 7fa51a15f9
4 changed files with 8 additions and 8 deletions

View File

@ -151,5 +151,5 @@ It is key that the operator carefully plans and considers the individual
performance needs of users and services within their OpenStack cloud when performance needs of users and services within their OpenStack cloud when
configuring and implementing any rate limiting functionality. configuring and implementing any rate limiting functionality.
Common solutions for providing rate-limiting are NGINX, HAProxy, OpenRepose, or Common solutions for providing rate-limiting are Nginx, HAProxy, OpenRepose, or
Apache Modules such as mod_ratelimit, mod_qos, or mod_security. Apache Modules such as mod_ratelimit, mod_qos, or mod_security.

View File

@ -42,11 +42,11 @@ Basic web server configuration
The dashboard should be deployed as a Web Services Gateway The dashboard should be deployed as a Web Services Gateway
Interface (WSGI) application behind an HTTPS proxy such as Interface (WSGI) application behind an HTTPS proxy such as
Apache or nginx. If Apache is not already in use, we recommend Apache or Nginx. If Apache is not already in use, we recommend
nginx since it is lightweight and easier to configure Nginx since it is lightweight and easier to configure
correctly. correctly.
When using nginx, we recommend When using Nginx, we recommend
`gunicorn <http://docs.gunicorn.org/en/latest/deploy.html>`_ `gunicorn <http://docs.gunicorn.org/en/latest/deploy.html>`_
as the WSGI host with an appropriate number as the WSGI host with an appropriate number
of synchronous workers. When using Apache, we recommend of synchronous workers. When using Apache, we recommend

View File

@ -10,7 +10,7 @@ dashboard. The dashboard is rendering dynamic content resulting
directly from OpenStack API requests and front-end caching layers directly from OpenStack API requests and front-end caching layers
such as varnish can prevent the correct content from being such as varnish can prevent the correct content from being
displayed. In Django, static media is directly served from Apache displayed. In Django, static media is directly served from Apache
or nginx and already benefits from web host caching. or Nginx and already benefits from web host caching.
Session back end Session back end
~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~

View File

@ -12,7 +12,7 @@ that can be used for this purpose:
* `Pound <http://www.apsis.ch/pound>`_ * `Pound <http://www.apsis.ch/pound>`_
* `Stud <https://github.com/bumptech/stud>`_ * `Stud <https://github.com/bumptech/stud>`_
* `nginx <http://nginx.org/>`_ * `Nginx <http://nginx.org/>`_
* `Apache httpd <http://www.apache.org/>`_ * `Apache httpd <http://www.apache.org/>`_
In cases where software termination offers insufficient performance, In cases where software termination offers insufficient performance,
@ -209,10 +209,10 @@ However, it is not provided by default.
# Disabling this until we upgrade to HAProxy 1.5 # Disabling this until we upgrade to HAProxy 1.5
write-proxy = off write-proxy = off
nginx Nginx
----- -----
This nginx example requires TLS v1.1 or v1.2 for maximum security. The This Nginx example requires TLS v1.1 or v1.2 for maximum security. The
``ssl_ciphers`` line can be tweaked based on your needs, however this ``ssl_ciphers`` line can be tweaked based on your needs, however this
is a reasonable starting place. is a reasonable starting place.
The default configuration file is ``/etc/nginx/nginx.conf``. The default configuration file is ``/etc/nginx/nginx.conf``.