darahayes

#Getting Started With Node

So... Enterprise development is a little crazy. I think he managed to give us a bare idea of what we're meant to do but he left out some really important things. So this is a post for people who might not be familiar with Node.js etc.

Firstly, it can be a bit of a pain to install properly. Luckily there's a great project called nvm (node version manager) that can make the installation and management of node versions on *nix really easy. nvm can be installed in a single line. Follow the instructions to install in the link.

Once installed you can install node and npm with the following

nvm install 4.2.3 #install node
nvm use 4.2.3 #tell nvm to place the installation in the right directories

darahayes

version: 0.0
os: linux
files:
  - source: /
    destination: /home/ec2-user/node
permissions:
  - object: /home/ec2-user
    owner: ec2-user
    group: ec2-user
    type:

darahayes

KMS Encrypt and Decrypt Filters for Ansible

This Gist shows how you can encrypt/decrypt variables with KMS during your Ansible playbook execution. While google searching I couldn't find anything useful on the subject.

Let's say your project has a folder of playbooks called plays.

In that folder, create a folder called filter_plugins and insert kms_filters.py (included in this gist)

darahayes

const http = require('http');
const memwatch = require('memwatch-next');
const heapdump = require('heapdump');

var server = http.createServer((req, res) => {
 for (var i=0; i<1000; i++) {
   server.on('request', function leakyfunc() {});
 }

 res.end('Hello World\n');

darahayes

const Hapi = require('hapi')
const Joi = require('joi')
const Boom = require('boom')

const server = new Hapi.Server()
server.connection({ host: 'localhost', port: 8000 })

server.register(
  [
    {

darahayes

const Hapi = require('hapi')
const Joi = require('joi')
const Boom = require('boom')

const server = new Hapi.Server()
server.connection({ host: 'localhost', port: 8000 })

server.register(
  [
    {

darahayes

*********************************************
SLIDES ARE AVAILABLE ONLINE ... MOSTLY
'http://events.linuxfoundation.org/events/node-interactive/program/agenda'
*********************************************

// there is a node certification coming
'https://nodejs.org/en/foundation/education/'

// interesting talks
- 'taking your server to ludicrous speed': 'http://sched.co/AtiP'

darahayes

apiVersion: v1
data:
  broker-config: |
    registry:
      - type: "dockerhub"
        name: "dh"
        url: "https://registry.hub.docker.com"
        org: "aerogearcatalog"
        tag: "latest"
        white_list:

darahayes

Commit Message Guidelines

This project has rules for commit messages (based on Conventional Commits). There are several reasons for this:

• Commit messages are more readable, especially when looking through the project history.
• Commit messages describe whether a major, minor or patch change has been introduced (see semver.org)
• Commit messages can be used to generate a changelog.

Commit Message Format

Each commit message consists of a header, an optional body and an an optional footer. The header has a special

darahayes

const knex = require('knex')

const db = knex({
  client: 'pg',
  connection: {
    'user': 'postgresql',
    'password': 'postgres',
    'database': 'memeolist_db',
    'host': '127.0.0.1',
    'port': '15432'