Closed giulioprovasi closed 9 years ago
Uh, you have a lot of provisioners. =)
The reason to trigger the proxy configurations after provisioner runs is that it is a common case to install npm, PEAR, git, etc. using a provisioner, while the base box doesn't have them. So you can first install for example npm with one provisioner, and then use it with proxies already configured in another one, without the need to run vagrant provision
multiple times.
I guess we could ensure we only run the configuration once, but this is the first time anyone ever complains about this. :) If you feel this would be needed, I'm happy to take a look at a PR.
I understand and it's not a problem indeed :), I was just curious about why it ran so frequently. I have a lot of provisioners as I tried to start a minimalist machine and add stuffs only by provisioning them.
I think a more common approach is to have one (or few anyway) provisioner run that does more things. I prefer to use a configuration management tool (Chef, Puppet, Ansible, ...) if a shell script is not trivial.
I get your point, I am just starting using all those provisioning tools, so for this time the use of vagrant provisioners was far more easy, but I'll get into Chef/Puppet as soon as I can
When using the plugin, here what my
vagrant up
looks like :How comes that each time that a provisioner is ran, the proxy updates is invoked ?
Here's my conf:
And my vagrant file :