ansible-role-nginx/handlers/main.yml

---
- name: restart nginx
  service: name=nginx state=restarted

- name: validate nginx configuration
  command: nginx -t -c /etc/nginx/nginx.conf
  changed_when: False
Initial commit. 2014-03-07 15:51:16 +01:00			`---`
			`- name: restart nginx`
Fixes #10: Better organize os-specific tasks. 2015-02-21 06:15:01 +01:00			`service: name=nginx state=restarted`
Addning handler for Nginx config validation: Although the 'validate' param was added for the deployment of /etc/nginx.conf - this validation process will only be triggered upon changes. So, if a vhost config is updated, but the main config isn't, the collective config will not be verified. I've added a new handler 'validate nginx configuration' and added this to the 'notify' param as a first list item for vhost config changes. Unfortunately, this will not protect against the deployment of malformed configuration, however it will prevent the restart of Nginx in such a situation (as the 'validate nginx configuration' handler should error out before the 'restart nginx' handler is called). 2015-12-22 17:36:11 +01:00
			`- name: validate nginx configuration`
Correcting nginx config path in validate handler 2015-12-22 18:07:47 +01:00			`command: nginx -t -c /etc/nginx/nginx.conf`
Addning handler for Nginx config validation: Although the 'validate' param was added for the deployment of /etc/nginx.conf - this validation process will only be triggered upon changes. So, if a vhost config is updated, but the main config isn't, the collective config will not be verified. I've added a new handler 'validate nginx configuration' and added this to the 'notify' param as a first list item for vhost config changes. Unfortunately, this will not protect against the deployment of malformed configuration, however it will prevent the restart of Nginx in such a situation (as the 'validate nginx configuration' handler should error out before the 'restart nginx' handler is called). 2015-12-22 17:36:11 +01:00			`changed_when: False`