My 5-minute "flash talk" for the House of Representatives' 2014 Legislative Data and Transparency Conference.
- Introduction
- Can't not talk about GitHub
My 5-minute "flash talk" for the House of Representatives' 2014 Legislative Data and Transparency Conference.
I've recently shifted from a straight engineering job to a job with a "dev/ops" title. What I have discovered in operations land depresses me. The shoemaker's children are going unshod. Operations software is terrible.
What's driving me craziest right now is my monitoring system.
What I have right now is Nagios.
license: gpl-3.0 |
A D3 recreation of David Taylor's visualization The meteoric rise of boys' names ending in 'n'.
The chart shows the number of children born with names ending in each letter. Adjust the slider to change the year. Toggle the checkboxes to show boys, girls, or both.
the goal: to do fast virtual host routing, e.g. to have a single process on a machine listening on port 80 and proxying data based on HTTP Host to other non-port-80 web processes on the same machine
many people use nginx for this because nginx is faster than node is currently for data-heavy applications (see below)
they use the JS proxies from https://github.com/substack/bouncy/tree/master/bench
When the directory structure of your Node.js application (not library!) has some depth, you end up with a lot of annoying relative paths in your require calls like:
const Article = require('../../../../app/models/article');
Those suck for maintenance and they're ugly.
Testing out fedor's SSL enhancements. You don't notice the difference... At first!
Once you adjust ciphers to disable ECDH, then you get the nice surprise.
Running an http server that acts as a proxy to an SSL server, all running on localhost
.
npm init
)if (req.url~ "^/[^/]+/-/[^/]+\.tgz") { | |
set req.url = regsub(req.url, "^/([^/]+)/-/([^/]+\.tgz)", "/isaacs/public/npm/$1/_attachments/$2"); | |
} else { | |
set req.url = "/isaacs/public/npm/" req.url "/doc.json"; | |
} |