Clone provisioners to a separate location

[msaggiorato]

Site provisioners now get cloned into the site folders, and then executed in place. This makes GIT UIs think that the provisioner is actually the relevant repo to open.

An example of this is GitKraken having the www directory as a source of repositories.

This could be avoided by cloning the provisioners to a separate location (potentially avoiding several clones of the same provisioner) and then just executing them in the site folder.

[welcome[bot]]

Thanks for opening your first issue here! Be sure to follow the issue template and include your OS/Vagrant/VVV versions! Don't forget you can get support in the VVV slack at https://varyingvagrantvagrants.org/docs/en-US/slack/

Varying Vagrant Vagrants

VVV Slack Workspace

Join the VVV Slack Workspace

[tomjn]

This would require us to eiither create a brand new site template or incorporate it into VVV core, else we'd break all existing sites. Eitherway it's a breaking change that'd require a 4.0.

In the meantime if we're looking to fix the git UI issue then there are other solutions, such as letting people configure git clone paths and opening those in the editor rather than the entire site folder. I don't see much use for opening the entire folder when most people would have a better experience opening public_html or wp-content instead