Manual Proxy Overrides in an Automated Setup

Nginx Configuration¶

Ansible generates Nginx configuration files based on whether a Fully Qualified Domain Name (FQDN) is defined:

These files are fully managed by Ansible, meaning any manual changes will be lost when the playbook is re-applied.

Safe Manual Customization¶

Each Ansible-generated config file includes an explicit static file, which is created during the initial setup and never modified by Ansible after that.

Customize only the static file included in your dynamic configuration. Since this is not touched by Ansible, it will persist across playbook runs.

Important: After making changes, manually reload Nginx:

sudo systemctl reload nginx

Apache2 Configuration¶

Apache2 uses a similar setup to Nginx, with a slightly different directory structure.

Ansible-Managed Files¶

Ansible generates the main configuration file based on whether a Fully Qualified Domain Name (FQDN) is defined.
These files are overwritten on every playbook run — do not edit them manually.

Static Files for Manual Edits¶

Each Ansible config includes a static file created at setup and never modified afterward.
Place all manual changes here.

Note

Always make manual changes in the static file. These are explicitly included in the main Ansible config.

Reload Apache After Edits¶

sudo systemctl reload apache2