kgrvamsi

Stop all containers:

• docker ps -aq | xargs docker stop

Remove all containers:

• docker ps -aq | xargs docker rm

Remove all images:

• docker images -aq | xargs docker rmi

Remove all networks:

kgrvamsi

# System preparation
## Update system:
sudo apt-get update && sudo apt-get dist-upgrade -y

## Prepare for Docker-CE install:
sudo apt-get install -y \
  apt-transport-https \
  ca-certificates \
  curl \
  gnupg-agent \

kgrvamsi

kubectl get pods -n kube-system
NAME                                    READY   STATUS    RESTARTS   AGE
coredns-5c98db65d4-2xhgz                1/1     Running   0          10m
coredns-5c98db65d4-66frr                1/1     Running   0          10m
etcd-ubuntu-xenial                      1/1     Running   0          9m49s
kube-apiserver-ubuntu-xenial            1/1     Running   0          10m
kube-controller-manager-ubuntu-xenial   1/1     Running   0          9m48s
kube-flannel-ds-amd64-4lm5j             1/1     Running   0          7m47s
kube-proxy-vd54k                        1/1     Running   0          10m

kgrvamsi

# This is just a cheat sheet:

# On production
sudo -u postgres pg_dump database | gzip -9 > database.sql.gz

# On local
scp -C production:~/database.sql.gz
dropdb database && createdb database
gunzip < database.sql.gz | psql database

kgrvamsi

'Users hate change'

This week NN Group released a video by Jakob Nielson in which he attempts to help designers deal with the problem of customers being resistant to their new site/product redesign. The argument goes thusly:

1. Humans naturally resist change
2. Your change is for the better
3. Customers should just get used to it and stop complaining

There's slightly more to it than that, he caveats his argument with requiring you to have of course followed their best practices on product design, and allows for a period of customers being able to elect to continue to use the old site, although he says this is obviously only a temporary solution as you don't want to support both.

kgrvamsi

#!/bin/bash

## The following command starts Vault in development mode
## specifiying a root token value of 'root'
##
# VAULT_UI=true vault server -dev -dev-root-token-id="root"

## Login with root token
## Good for demo mode, should only be used on production cluster
## during initial configuration

kgrvamsi

How to setup Let's Encrypt for Nginx on Ubuntu 18.04 (including IPv6, HTTP/2 and A+ SLL rating)

---

Virtual hosts

Let's say you want to host domains first.com and second.com.

Create folders for their files:

kgrvamsi

import auth0 from 'auth0-js';
import history from './history';

export default class Auth {
  requestedScopes = 'openid profile email read:todos write:todos';

  // Please use your own credentials here
  auth0 = new auth0.WebAuth({
    domain: 'divyanshu.auth0.com',
    clientID: 'IcVGTI2AUvc49lnE0ltVemretrsI3y3P',

kgrvamsi

Links on microservices:

https://www.kennybastani.com/2017/01/building-event-driven-microservices.html https://wso2.com/whitepapers/event-driven-architecture-the-path-to-increased-agility-and-high-expandability/ https://content.pivotal.io/blog/how-to-deliver-an-event-driven-architecture https://solace.com/products https://hackernoon.com/event-driven-microservices-with-quebic-f65f99a5b25a https://dzone.com/articles/no-framework https://microservices.io/patterns/data/event-driven-architecture.html https://mapr.com/blog/event-driven-microservices-patterns/

kgrvamsi

package main

import (
	"os"
	"archive/tar"
	"log"
	"io"
	"compress/gzip"
)