sonukapoor

Git Commit Best Practices

Basic Rules

Commit Related Changes

A commit should be a wrapper for related changes. For example, fixing two different bugs should produce two separate commits. Small commits make it easier for other developers to understand the changes and roll them back if something went wrong. With tools like the staging area and the ability to stage only parts of a file, Git makes it easy to create very granular commits.

Commit Often

Committing often keeps your commits small and, again, helps you commit only related changes. Moreover, it allows you to share your code more frequently with others. That way it‘s easier for everyone to integrate changes regularly and avoid having merge conflicts. Having large commits and sharing them infrequently, in contrast, makes it hard to solve conflicts.

sonukapoor

https://run.plnkr.co/preview/ckf5hukqg000e3b6aom42idir/

sonukapoor

download and install font from https://github.com/abertsch/Menlo-for-Powerline
set your vs code font to: 

"terminal.external.osxExec": "iterm.app",
"terminal.integrated.shell.osx": "/bin/zsh",
"terminal.integrated.fontFamily": "Menlo for Powerline",

sonukapoor

Git rebase easy
  // make sure that you are on your branch
  git fetch origin
  git reset $(git merge-base master $(git branch --show-current))

Git download PR into new branch

  git fetch origin pull/2/head
  git checkout -b NEW_BRANCH_NAME FETCH_HEAD
  

sonukapoor

Comprehensive Introduction to @ngrx/store

By: @BTroncone

Also check out my lesson @ngrx/store in 10 minutes on egghead.io!

Update: Non-middleware examples have been updated to ngrx/store v2. More coming soon!

Table of Contents

sonukapoor

function showDate(){
  var date = new Date(),
    str = date.toUTCString();

  return str;
}

var orig = console.log;

console.log = function() {

sonukapoor

# Get all VS Code extensions:

code --list-extensions | xargs -L 1 echo code --install-extension

# My fav VS Code Extentions

code --install-extension Angular.ng-template
code --install-extension CoenraadS.bracket-pair-colorizer
code --install-extension SirTori.indenticator
code --install-extension WallabyJs.quokka-vscode

sonukapoor

-- nginx config
sudo vi /etc/nginx/nginx.conf

-- allow nginx communication with other ports
sudo setsebool -P httpd_can_network_connect 1

-- test nginx config
sudo nginx -t

-- check nginx log

sonukapoor

How to: Allow Node to bind to port 80 without sudo

TL;DR

Only do this if you understand the consequences: all node programs will be able to bind on ports < 1024

sudo setcap 'cap_net_bind_service=+ep' /usr/local/bin/node

Important: your node location may vary. Use which node to find it, or use it directly in the command:

sonukapoor

#!/bin/sh
#
# nginx - this script starts and stops the nginx daemon
#
# chkconfig:   - 85 15 
# description:  Nginx is an HTTP(S) server, HTTP(S) reverse \
#               proxy and IMAP/POP3 proxy server
# processname: nginx
# config:      /etc/nginx/nginx.conf
# config:      /etc/sysconfig/nginx