Sumeet Bhardwaj sumitsk20

Setup

git clone <repo>

clone the repository specified by ; this is similar to "checkout" in some other version control systems such as Subversion and CVS

Add colors to your ~/.gitconfig file:

Setting up and installing rbenv, ruby-build, rubies, rbenv-gemset, and bundler

This guide enables you to install (ruby-build) and use (rbenv) multiple versions of ruby, isolate project gems (gemsets and/or bundler), and automatically use appropriate combinations of rubies and gems.

TL;DR Demo

# Ensure system is in ship-shape.

aptitude install git zsh libssl-dev zlib1g-dev libreadline-dev libyaml-dev

ANNOUNCEMENT

I have moved this over to the Tech Interview Cheat Sheet Repo and has been expanded and even has code challenges you can run and practice against!

\

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.

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)

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

	''' quick example showing how to attach a pdf to multipart messages
	and then send them from SES via boto
	'''

	from email.mime.text import MIMEText
	from email.mime.application import MIMEApplication
	from email.mime.multipart import MIMEMultipart

	import boto

	upstream upstream-apache2 {
	server 127.0.0.1:8080;
	}

	upstream upstream-nodejs {
	server 127.0.0.1:3000;
	}

	server {
	listen 80;

	#!/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

	#!/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