#nodeconf

NodeConf Remote 2021 is the biggest Node.js conference in Europe, taking place 18 - 21 October 2021. Registration is open. #NodeConf #Nodejs #NodeConfRemote

NodeConf Remote 2021 is the biggest Node.js conference in Europe, taking place 18 – 21 October.  (more…)

Tirsdag klokka 07:30 nøt vi en rolig frokost med utsikt over hagene. Hjorter som beitet, harer som hoppet og konferansedeltakere fra USA, som gikk rundt og sa "Good morning, how y'all doing?". Ah, such bliss!

Dagens første foredrag var en ganske interessant fortelling om koding av nodemoduler i C++, som selv Fossegrimen klarte å følge med på. Mike Tunniclife fra IBM foredro.

Suz Hinton fortalte om hvordan hun har gått fra å lage ting til å lage ting for å hjelpe folk med å lage ting. Som hun selv sier: "Many people want to hack chips, not many people want to code C/C++". Hun står som ansvarlig for avrgirl, et prosjekt som er tenkt å gjøre det enklere å bruke Node.js til å programmere microchips.

Kelsey Breseman dro på med en skildring av hvor vanskelig det er å vite hvordan man skal utvikle et åpent produkt, særlig med tanke på hva man gjør når produktet er sluppet. En aldri så liten filosofitime der altså.

Thomas Watson er en artig fyr fra Danmark, som viste hvordan han har hacket Apples Airplay. Han presenterte eksempler på hvordan han klarte å late som om EDB-maskinen hans var en Airplay-enhet, slik at vi kunne laste bilder opp på maskinen hans (og mye mer). Fiffig.

En sløy amerikaner fra IBM fortalte oss om sine erfaringer med å lage et alarmsystem for hytta si ved bruk av Node.js, Arduino og diverse smådeler til en totalverdi på $100. Det synes jaffal Fossegrimen var gøy å se på.

Med italiensk bravur og dramaturgi, støttet av minst fire doble espresso, viste Luka Maraschi oss hvordan han feilsøkte i nattens mulm, etter at produksjonssiten hans gikk ned klokka 3 om morgenen. Han var flink til å fortelle. Det er J Edgar enig i.

An npm registry dev-ops deep-dive.

NodeConf 2014 was fantastic! I love the format, and the location. It was my first NodeConf, and I enjoyed every bit of it.

Except the Internet connection.

While the WiFi itself was fine, with hundreds of us trying to download packages from the npm registry at the same time, the tiny Internet connection at Walker Creek Ranch left something to be desired. Some folks set up their own registry mirrors on the local network, which was great, but that meant finding their URLs on whiteboards here and there.

reginabox is a solution to this, providing discoverable npm registry mirrors for situations like NodeConf, where the network is great, but the Internet bandwidth is limited.

If you're going to NodeConf 2015 at Walker Creek Ranch, you should install reginabox on the machine that you'll be bringing:

$ [sudo] npm i -g reginabox

Then, once you're at the event, you can run this to discover local npm registry mirrors:

$ reginabox discover

This will list available mirrors and how up-to-date they are. Then, once you've chosen a suitable one, you can set it as your registry, and you're all set:

$ npm config set registry <url>

That's all there is to it! We'll be bringing at least one dedicated mirror machine, but if you'd like to provide your own, keep reading. The process is pretty simple.

You'll want to get this started a few days before the day you leave for NodeConf, as the mirroring process can take days. Get yourself a big hard drive (2TB should be sufficient to handle the registry for the foreseeable future), and a machine to host it, with WiFi. You'll need a case-sensitive filesystem on the drive. Once your OS installed and the hard drive is mounted, install node.js and reginabox as above.

Then, in a directory that's on the hard drive, do this:

$ reginabox mirror

This will kick off the mirroring process. It's running registry-static behind the scenes to download the entire registry to disk and keep up to date with changes as long as it's running. It also runs an HTTP server that serves up all the tarballs and metadata, and acts as a registry server, which is exposed on the network via mDNS, so that it's discoverable by reginabox discover.

Make sure you run this right up until the time you leave for the event, and then start running it again as soon as you get there, so that you minimize the amount of data that needs to be transferred using the event's Internet connection. It's probably best to wrap it up in some kind of process monitoring like upstart or monit, as you'll pretty much always want this to be running.