Re-ordering the tasks in this way (having the vhosts deployed first) allows the 'validate' param to collectively check the deployed Nginx config. Deploying vhosts after makes it hard to check their validity, as Nginx's config checking will operate on a "master" configuration that includes others (checking those included, also) but would error out when checking these individual configs if they do not contain a fully working Nginx config (which they often don't, due to their nature).pull/36/head
parent
1f99c72698
commit
cc5114dc4f
Reference in new issue