Last modified: 2014-11-17 21:35:40 UTC
The image doesn't include npm and vagrant-proxyconf can only configure npm's proxy once it is installed. This means that npm needs to be run on "vagrant provision".
This seems like a legitimate bug, but I have a hard time figuring out what is actually broken. What are you expecting, and what is the actual behavior?
hexmode: Can you please answer comment 1?
(In reply to Ori Livneh from comment #1) > This seems like a legitimate bug, but I have a hard time figuring out what > is actually broken. What are you expecting, and what is the actual behavior? I'm working on other things right now, so I can't say for sure what the problem is, but as I recall, mw-vagrant would try to invoke npm before its proxy was configured. Re-reading my explanation, though, I'm not sure how npm could be run without a proxy (since evidently apt needs to have its proxy configured). Hrm... but perhaps this is an interaction between vagrant-proxyconf and mw-vagrant. Maybe this fails if you enable the ve role and then run provision. npm would then be installed but the npm-based installations would fail because its proxy isn't configured. In this case, If vagrant-proxyconf might (or might not, I don't recall) configure the npm proxy on the next provision. Would mw-vagrant try to re-run the npm installations after that? Sorry, I'll try to provide a better explanation after I retry the scenario.
Bulk unassigning bugs from Ori.
