joseluisq

Docker Swarm Mode Ports

Starting with 1.12 in July 2016, Docker Swarm Mode is a built-in solution with built-in key/value store. Easier to get started, and fewer ports to configure.

Inbound Traffic for Swarm Management

• TCP port 2377 for cluster management & raft sync communications
• TCP and UDP port 7946 for "control plane" gossip discovery communication between all nodes
• UDP port 4789 for "data plane" VXLAN overlay network traffic
• IP Protocol 50 (ESP) if you plan on using overlay network with the encryption option

AWS Security Group Example

joseluisq

#!/bin/bash

# remove exited containers:
docker ps --filter status=dead --filter status=exited -aq | xargs -r docker rm -v
    
# remove unused images:
docker images --no-trunc | grep '<none>' | awk '{ print $3 }' | xargs -r docker rmi

# remove unused volumes:
find '/var/lib/docker/volumes/' -mindepth 1 -maxdepth 1 -type d | grep -vFf <(

joseluisq

#Linux - Production Server Setup The principle of running a server in production is to run only what is needed. This keeps the server load to a minimum and reduces the security footprint.

See also http://plusbryan.com/my-first-5-minutes-on-a-server-or-essential-security-for-linux-servers

##Setup the Domain Name (DNS) Point the dns address at the ip address of your server. If the server is rented you should already have a static ip address. If the machine is on your local network you may have to sudo nano /etc/network/interfaces to edit the ip address file. Your setup should be like:

iface eth0 inet static

joseluisq

BLACK  => "\033[30m",
RED    => "\033[31m",
GREEN  => "\033[32m",
YELLOW => "\033[33m",
BLUE   => "\033[34m",
PURPLE => "\033[35m",
CYAN   => "\033[36m",
WHITE  => "\033[37m",

# background color

joseluisq

iTerm2 Shortcuts

Tab navigation

• open new tab: Cmd + t
• next tab: Cmd + Shift + ]
• previous tab: Cmd + Shift + [

Pane navigation

joseluisq

// Array literal (= []) is faster than Array constructor (new Array())
// http://jsperf.com/new-array-vs-literal/15
var array = [];

// Object literal (={}) is faster than Object constructor (new Object())
// http://jsperf.com/new-array-vs-literal/26
var obj = {};

// property === undefined is faster than hasOwnProperty(property)
// Note: don't use this in cases where 'undefined' is a possible value for your properties

joseluisq

var Benchmark = require('benchmark');
var expect = require('expect');
var suite = new Benchmark.Suite;

var testArray = [1,2,3,4,5,6,7,8,9,10,11,12,13];
var resultat = [2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26];

suite
    .add('forHoley', () => forHoley(testArray))
    .add('forPush', () => forPush(testArray))

joseluisq

const Benchmark = require('benchmark')
const co = require('co')
const bluebird = require('bluebird')

const suite = new Benchmark.Suite

suite
  .add('co generators', {
    defer: true,
    fn: deferred => {

joseluisq

Top-level await is a footgun 👣🔫

Follow-ups:

• Why imperative imports are slower than declarative imports
• Dynamic module loading done right
• Non-deterministic module ordering is an even bigger footgun

As the creator of Rollup I often get cc'd on discussions about JavaScript modules and their semantics. Recently I've found myself in various conversations about top-level await.

joseluisq

^ = Ctrl key M = Alt key

^G      (F1)            Display this help text
^X      (F2)            Close the current file buffer / Exit from nano
^O      (F3)            Write the current file to disk
^J      (F4)            Justify the current paragraph

^R      (F5)            Insert another file into the current one