You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Could we please have a shared local npm mirror for the next campjs?
I understand that some people had npmd or their own copy of the npm couchdb database but it would be great if this could be set up via transparent proxy for everyone to use, to reduce the load on the external connection, and make it fast for people to install packages to follow along with talks/workshops
The text was updated successfully, but these errors were encountered:
We did have a local npm mirror on a local server at campjs. The issue was that the wifi contention meant that people simply couldn't get to the local mirror.
We posted the details of how to access the local npm repo at http://campjs (a local DNS entry).
I think having a transparent proxy to the local mirror is a great idea though as people would need to use something like npmrc to switch their npm config around.
Some people had issues with the DNS entries (custom DNS servers). Would be good to have something like: http://npm.campjs.com which would resolve locally and remotely to a 192.x.x.x address.
We're chatting about how to improve the wifi connectivity for next year at this issue too if you have any ideas: #3
I'm also currently looking into the feasibility of a local bower.io repo too for client-side scripts for next year too.
Could we please have a shared local npm mirror for the next campjs?
I understand that some people had npmd or their own copy of the npm couchdb database but it would be great if this could be set up via transparent proxy for everyone to use, to reduce the load on the external connection, and make it fast for people to install packages to follow along with talks/workshops
The text was updated successfully, but these errors were encountered: