nginx(role): document arguments in README for better discoverability
Document the role arguments in the README instead of in the argument_specs for better discoverability and readability.
This commit is contained in:
parent
2e9f73b46b
commit
4adf39d969
2 changed files with 23 additions and 26 deletions
roles/nginx
|
@ -18,7 +18,29 @@ The following distributions are supported:
|
||||||
|
|
||||||
## Required Arguments
|
## Required Arguments
|
||||||
|
|
||||||
For the required arguments look at the [`argument_specs.yaml`](./meta/argument_specs.yaml).
|
None.
|
||||||
|
|
||||||
|
## Optional Arguments
|
||||||
|
|
||||||
|
- `nginx__deploy_redirect_conf`: Whether or not to deploy a config redirecting from HTTP to HTTPS, while still forwarding the `/.well-known/acme-challenge/` to localhost Port 31820 for certificate issuing.
|
||||||
|
See [`files/redirect.conf`](./files/redirect.conf) for the configuration that would be deployed.
|
||||||
|
Defaults to `true`.
|
||||||
|
- `nginx__deploy_tls_conf`: Whether or not to deploy a config configuring some TLS settings reasonably.
|
||||||
|
See [`files/tls.conf`](./files/tls.conf) for the configuration that would be deployed.
|
||||||
|
Defaults to `true`.
|
||||||
|
- `nginx__deploy_logging_conf`: Whether or not to deploy a config configuring logging to journald.
|
||||||
|
See [`files/logging.conf`](./files/logging.conf) for the configuration that would be deployed.
|
||||||
|
Defaults to `true`.
|
||||||
|
- `nginx__configurations`: List of nginx configurations to ensure are deployed.
|
||||||
|
- `nginx__configurations.*.name`: This name with `.conf` appended will be used for the configurations file name under `/etc/nginx/conf.d/`.
|
||||||
|
`tls` and `redirect` are reserved names.
|
||||||
|
- `nginx__configurations.*.content`: This configurations content.
|
||||||
|
- `nginx__use_custom_nginx_conf`: Whether or not to use a custom `/etc/nginx/nginx.conf`.
|
||||||
|
If set to true, you must provide the content for a custom `nginx.conf` via `nginx__custom_nginx_conf`.
|
||||||
|
Defaults to `false`.
|
||||||
|
- `nginx__custom_nginx_conf`: The content to use for the custom `nginx.conf`.
|
||||||
|
Needs `nginx__use_custom_nginx_conf` to be set to true to work.
|
||||||
|
You should probably still make sure that your custom `nginx.conf` includes `/etc/nginx/conf.d/*.conf`, so that the other configuration files still work.
|
||||||
|
|
||||||
## `hosts`
|
## `hosts`
|
||||||
|
|
||||||
|
|
|
@ -2,21 +2,14 @@ argument_specs:
|
||||||
main:
|
main:
|
||||||
options:
|
options:
|
||||||
nginx__deploy_redirect_conf:
|
nginx__deploy_redirect_conf:
|
||||||
description: >-
|
|
||||||
Whether or not to deploy a `redirect.conf` to
|
|
||||||
`/etc/nginx/conf.d/redirect.conf`.
|
|
||||||
type: bool
|
type: bool
|
||||||
required: false
|
required: false
|
||||||
default: true
|
default: true
|
||||||
nginx__deploy_tls_conf:
|
nginx__deploy_tls_conf:
|
||||||
description: >-
|
|
||||||
Whether or not to deploy a `tls.conf` to `/etc/nginx/conf.d/tls.conf`.
|
|
||||||
type: bool
|
type: bool
|
||||||
required: false
|
required: false
|
||||||
default: true
|
default: true
|
||||||
nginx__deploy_logging_conf:
|
nginx__deploy_logging_conf:
|
||||||
description: >-
|
|
||||||
Whether or not to deploy a `logging.conf` to `/etc/nginx/conf.d/logging.conf`.
|
|
||||||
type: bool
|
type: bool
|
||||||
required: false
|
required: false
|
||||||
default: true
|
default: true
|
||||||
|
@ -28,34 +21,16 @@ argument_specs:
|
||||||
default: [ ]
|
default: [ ]
|
||||||
options:
|
options:
|
||||||
name:
|
name:
|
||||||
description: >-
|
|
||||||
The name of the configuration file, where the configuration should
|
|
||||||
be deployed to. The file will be placed under `/etc/nginx/conf.d/`
|
|
||||||
and `.conf` will be appended to the given name. So in the end the
|
|
||||||
path will be like this: `/etc/nginx/conf.d/\{\{ name \}\}.conf`.
|
|
||||||
Note that the names `tls` and `redirect` aren't allowed.
|
|
||||||
type: str
|
type: str
|
||||||
required: true
|
required: true
|
||||||
content:
|
content:
|
||||||
description: The content of the configuration.
|
|
||||||
type: str
|
type: str
|
||||||
required: true
|
required: true
|
||||||
nginx__use_custom_nginx_conf:
|
nginx__use_custom_nginx_conf:
|
||||||
description: >-
|
|
||||||
Whether or not to use a custom `/etc/nginx/nginx.conf`. If set to
|
|
||||||
true, you must provide a custom `nginx.conf` via
|
|
||||||
`nginx__custom_nginx_conf`.
|
|
||||||
type: bool
|
type: bool
|
||||||
required: false
|
required: false
|
||||||
default: false
|
default: false
|
||||||
nginx__custom_nginx_conf:
|
nginx__custom_nginx_conf:
|
||||||
description: >-
|
|
||||||
The value for a `nginx.conf` to be placed at `/etc/nginx/nginx.conf`.
|
|
||||||
You must set `nginx__use_custom_nginx_conf` to true for this value to
|
|
||||||
be used.
|
|
||||||
You should probably make sure that your custom `nginx.conf` still
|
|
||||||
includes `/etc/nginx/conf.d/*.conf` so that the configuration provided
|
|
||||||
using `nginx__configurations` still work.
|
|
||||||
type: str
|
type: str
|
||||||
required: false
|
required: false
|
||||||
default: ""
|
default: ""
|
||||||
|
|
Loading…
Add table
Reference in a new issue