Sumeet Bhardwaj sumitsk20

Node.js Deployment

Steps to deploy a Node.js app to DigitalOcean using PM2, NGINX as a reverse proxy and an SSL from LetsEncrypt

1. Sign up for Digital Ocean

If you use the referal link below, you get $10 free (1 or 2 months) https://m.do.co/c/5424d440c63a

2. Create a droplet and log in via ssh

I will be using the root user, but would suggest creating a new user

Handling Multiple Github Accounts on MacOS

The only way I've succeeded so far is to employ SSH.

Assuming you are new to this like me, first I'd like to share with you that your Mac has a SSH config file in a .ssh directory. The config file is where you draw relations of your SSH keys to each GitHub (or Bitbucket) account, and all your SSH keys generated are saved into .ssh directory by default. You can navigate to it by running cd ~/.ssh within your terminal, open the config file with any editor, and it should look something like this:

Host *
 AddKeysToAgent yes

> UseKeyChain yes

If anyone is interested in setting up their system to automatically (or manually) sign their git commits with their GPG key, here are the steps:

Generate and add your key to GitHub
$ git config --global commit.gpgsign true ([OPTIONAL] every commit will now be signed)
$ git config --global user.signingkey ABCDEF01 (where ABCDEF01 is the fingerprint of the key to use)
$ git config --global alias.logs "log --show-signature" (now available as $ git logs)
$ git config --global alias.cis "commit -S" (optional if global signing is false)
$ echo "Some content" >> example.txt
$ git add example.txt
$ git cis -m "This commit is signed by a GPG key." (regular commit will work if global signing is enabled)

Using Graph Analysis to Design Microservice Architectures in the Cloud

This interactive Neo4j graph tutorial covers how to use graph analysis to find software modules that are highly centralized, making good candidates to be decomposed into microservices.

	# Reference: https://www.exclamationlabs.com/blog/continuous-deployment-to-npm-using-gitlab-ci/

	# GitLab uses docker in the background, so we need to specify the
	# image versions. This is useful because we're freely to use
	# multiple node versions to work with it. They come from the docker
	# repo.
	# Uses NodeJS V 9.4.0
	image: node:9.4.0

	# And to cache them as well.

	"""
	Middleware to log all requests and responses.
	Uses a logger configured by the name of django.request
	to log all requests and responses according to configuration
	specified for django.request.
	"""
	# import json
	import logging
	from django.utils.deprecation import MiddlewareMixin

	# Generate a new pgp key: (better to use gpg2 instead of gpg in all below commands)
	gpg --gen-key
	# maybe you need some random work in your OS to generate a key. so run this command: `find ./* /home/username -type d \| xargs grep some_random_string > /dev/null`

	# check current keys:
	gpg --list-secret-keys --keyid-format LONG

	# See your gpg public key:
	gpg --armor --export YOUR_KEY_ID
	# YOUR_KEY_ID is the hash in front of `sec` in previous command. (for example sec 4096R/234FAA343232333 => key id is: 234FAA343232333)

	#!/bin/sh
	set -e
	HOST=localhost
	DB=test-entd-products
	COL=asimproducts

	S3PATH="s3://mongodb-backups-test1-entd/$DB/$COL/"
	S3BACKUP=$S3PATH`date +"%Y%m%d_%H%M%S"`.dump.gz
	S3LATEST=$S3PATH"latest".dump.gz
	/usr/bin/aws s3 mb $S3PATH

	#!/bin/sh

	# Make sure to:
	# 1) Name this file `backup.sh` and place it in /home/ubuntu
	# 2) Run sudo apt-get install awscli to install the AWSCLI
	# 3) Run aws configure (enter s3-authorized IAM user and specify region)
	# 4) Fill in DB host + name
	# 5) Create S3 bucket for the backups and fill it in below (set a lifecycle rule to expire files older than X days in the bucket)
	# 6) Run chmod +x backup.sh
	# 7) Test it out via ./backup.sh

	upstream upstream-apache2 {
	server 127.0.0.1:8080;
	}

	upstream upstream-nodejs {
	server 127.0.0.1:3000;
	}

	server {
	listen 80;