Runs the states to install nginx, configure the common files, and the users.

``nginx.common``

Ensures standard nginx files are in place, and configures enabled sites.

``nginx.luajit2``

Installs luajit.

``nginx.openresty``

Installs openresty.

``nginx.package``

Installs the nginx package via package manager.

``nginx.source``

Installs nginx via the source files.

``nginx.users``

Installs apache utils, and configures nginx users specified in the pillar.

This requires `basicauth <https://github.com/saltstack/salt-contrib/blob/master/modules/basicauth.py>`_

from `salt-contrib <https://github.com/saltstack/salt-contrib/>`_ (either add it to your salt or ship

this single file in your `_modules` directory see `Dynamic Module Distribution

<https://docs.saltstack.com/en/latest/ref/file_server/dynamic-modules.html>`_

Next-generation, alternate approach

The following states provide an alternate approach to managing Nginx and Nginx

servers, as well as code organization. Please provide feedback by filing issues,

discussing in ``#salt`` in Freenode and the mailing list as normal.

.. contents::

:local:

``nginx.ng``

Meta-state for inclusion of all ng states.

**Note:** nginx.ng requires the merge parameter of salt.modules.pillar.get(),

``nginx.ng.pkg``

``nginx.ng.src``

``nginx.ng.certificates``

``nginx.ng.config``

``nginx.ng.service``

``nginx.ng.servers_config``

``nginx.ng.servers``

``nginx.ng.passenger``

There are a variety of approaches on the usage of pillar and templates as seen in the `saltstack-formulas <https://github.com/saltstack-formulas>`_' repositories. `Some <https://github.com/saltstack-formulas/nginx-formula/pull/18>`_ `developments <https://github.com/saltstack-formulas/php-formula/pull/14>`_ stress the initial purpose of pillar data into a storage for most of the possible variables for a determined system configuration. This, in my opinion, is shifting too much load from the original template files approach. Adding up some `non-trivial Jinja <https://github.com/spsoit/nginx-formula/blob/81de880fe0276dd9488ffa15bc78944c0fc2b919/nginx/ng/files/nginx.conf>`_ code as essential part of composing the state file definitely makes SaltStack state files (hence formulas) more difficult to read. The extreme of this approach is that we could end up with a new render mechanism, implemented in Jinja, storing everything needed in pillar data to compose configurations. Additionally, we are establishing a strong dependency with the Jinja renderer.

- nginx.ng

{% from 'nginx/ng/map.jinja' import nginx with context %}

{% from 'nginx/ng/map.jinja' import nginx, sls_block with context %}

{% from "nginx/map.jinja" import nginx as nginx_map with context %}

- nginx.common

{% if salt['pillar.get']('nginx:use_upstart', nginx_map['use_upstart']) %}

- nginx.upstart

{% elif salt['pillar.get']('nginx:use_sysvinit', nginx_map['use_sysvinit']) %}

- nginx.sysvinit

{% endif %}

{% if pillar.get('nginx', {}).get('user_auth_enabled', true) %}

- nginx.users

{% endif %}

{% if pillar.get('nginx', {}).get('install_from_source', false) %}

- nginx.source

{% else %}

- nginx.package

{% endif -%}