Local Networks and Cacheing.

[mikeal]

We need to work out the best way to distribute and update the workshoppers and other modules in the local network.

What I'm think is:

• Each room has its own network and its own npm cache. These local wireless networks are not connected to the internet, only the npm cache is connected.
• The regular wireless network at the camp is still up, seperate, and hopefully connected to the internet.

I think it's important that the presenters be able to update the workshopper packages during and between the sessions.

Thoughts: @substack @maxogden @dominictarr @isaacs

[dominictarr]

An entire npm cache is probably overkill, what we did last time is a simple server that served a tarball which included the node_modules we'd need for the workshop. Then we'd write a one line command to install that on the board:

curl 192.164.0.100:8000/ | tar -xz

much easier, + only one round trip. for updates, you could still do it the normal way, github, npm etc, and then reinstall on to the computer that is serving the workshop.

If we are trying to be gentle to the network I think this is both less IO, it's also much simpler than an entire npm cache.

[mikeal]

The main reason I'd like a full cache is just so that publishing doesn't get blocked. There's a much bigger focus on publishing new modules this year and I just don't want anything to hold up the feeling someone has when they publish a new module :)

[dominictarr]

good point.