search

tmatilai / vagrant-proxyconf

Vagrant plugin that configures the virtual machine to use proxies
MIT License
531 stars 74 forks source link

npm support not documented #61

Closed mylesbarros closed 10 years ago

mylesbarros commented 10 years ago

Support for npm proxy configuration exists within the plugin but making use of it is not described in the README.md file as it is for apt and yum. Unfortunately its usage is not self-evident.

tmatilai commented 10 years ago

The NPM support is totally automatic. It will kick in if npm executable is found, also after any provisioner run.

Suggestions how to improve the documentation are highly welcome. Unfortunately I don't personally have much FOSS time before May/June.

johnbellone commented 10 years ago

@mylesbarros Do you think there just needs to be something in README?

mylesbarros commented 10 years ago

Potentially. I'm currently relying on vagrant-proxyconf to circumvent a corporate firewall for development purposes and it's currently failing on npm commands. Whatever might be causing it my first approach was to climb through the source to determine usages for npm and, based on what I found there, attempted to model a manual npm proxy on my existing apt proxy.

As such a mention in the README that npm is automatic might prevent future users from making my mistakes.

tmatilai commented 10 years ago

@mylesbarros, the next release will fix two bugs with npm, see #57 and #59. If you could test it (instructions in the wiki), it would really help.

mylesbarros commented 10 years ago

I would be happy to test it - I'll keep an eye out for the next release.

tmatilai commented 10 years ago

I'm closing this, but as said, documentation improvements are happily accepted.