This is the best way I found to tackle the problem of custom directives, trying to
avoid common usage of module involve hacking the module/template to be able place
custom directives.
Right now support was added only for location context (default and custom ones),
it expects a hash with key value and it's supported on all current location types.
Added an example inside location.pp, usage it's pretty easy.
- Include the port in the listen directive
- Add an optional $server_name parameter to nginx::resource::vhost so
server_name doesn't have to match the resource's name. This allows
the creation of multiple vhosts with the same server_name that listen
on different ports.
Add a proxy_read_timeout parameter to set the read timeout setting
per-location. The parameter can also be passed when declaring a vhost,
in which case it will apply to the root location.
Try_files is how NGINX files the files to serve particularly in a
fallback mode. Using an array for try_files will interate through
these options in the generated configuration file.