thomasbabuj

1. Change your database RDS instance security group to allow your machine to access it.
   • Add your ip to the security group to acces the instance via Postgres.
2. Make a copy of the database using pg_dump
   • $ pg_dump -h <public dns> -U <my username> -f <name of dump file .sql> <name of my database>
   • you will be asked for postgressql password.
   • a dump file(.sql) will be created
3. Restore that dump file to your local database.
   • but you might need to drop the database and create it first
   • $ psql -U <postgresql username> -d <database name> -f <dump file that you want to restore>

• the database is restored

thomasbabuj

class CircuitBreaker {
  constructor(request) {
    this.request = request
    this.state = "CLOSED"
    this.failureThreshold = 3
    this.failureCount = 0
    this.successThreshold = 2
    this.successCount = 0
    this.timeout = 6000
    this.nextAttempt = Date.now()

thomasbabuj

// List all files in a directory in Node.js recursively in a synchronous fashion
var walkSync = function(dir, filelist) {
  var fs = fs || require('fs'),
      files = fs.readdirSync(dir);
  filelist = filelist || [];
  files.forEach(function(file) {
    if (fs.statSync(dir + file).isDirectory()) {
      filelist = walkSync(dir + file + '/', filelist);
    }
    else {

thomasbabuj

Manual Git Flow for a Feature Branch from the CLI

Brief Context

Back in 2010, Vincent Driessen wrote a post called A successful Git branching model. Besides being extremely well drafted and clear in it's intention, the post goes into great detail about Git branching strategies and release management. The model that Vincent (sobriquet "nvie") came up with was popularized as git-flow.

thomasbabuj

#!/bin/bash
docker rm --force $(docker ps --all -q)
docker rmi --force $(docker images --all -q)

thomasbabuj

Sequelize + Express Starter Guide

Based off of: http://docs.sequelizejs.com/en/1.7.0/articles/express/

Create your project directory

Create and initialize your a directory for your Express application.

$ mkdir sequelize-demo

thomasbabuj

Default

Powerlevel9k

thomasbabuj

export class SyncPath {
  constructor(rootRef, path) {
    this._rootRef = rootRef;
    this.user = this._rootRef.getAuth();
    this._userDataRef = this._rootRef.child(path).child(this.user.uid);
    this.data = {};
    this._userDataRef.on('value', (snap) => this.data = snap.val() || {});
  }
  keys() {
    return Object.keys(this.data);

thomasbabuj

REST, RESTful API Quick Reference

A good API is not just easy to use but also hard to misuse.

Ressources

• Version your API
  • Path: /v1/users
  • Subdomain: api.v1.example.com/users

thomasbabuj

This article has been given a more permanent home on my blog. Also, since it was first written, the development of the Promises/A+ specification has made the original emphasis on Promises/A seem somewhat outdated.

You're Missing the Point of Promises

Promises are a software abstraction that makes working with asynchronous operations much more pleasant. In the most basic definition, your code will move from continuation-passing style:

getTweetsFor("domenic", function (err, results) {
 // the rest of your code goes here.