Currently the httpd configuration processing work by parsing an existing configuration et replacing one key token within it, while the nginx configuration work by simply creating a file that should be included in the main configuration.
Any insight into why thoses different processes ?
The httpd-one is not very practical with managed configuration files like with cfn-init which will fight with the acm configuration management
Currently the httpd configuration processing work by parsing an existing configuration et replacing one key token within it, while the nginx configuration work by simply creating a file that should be included in the main configuration.
Any insight into why thoses different processes ?
The httpd-one is not very practical with managed configuration files like with cfn-init which will fight with the acm configuration management