I have been using Ubuntu for most of my development works for a long time. But recently I also started working on a Mac on one of my projects. This was the first time I was using it. Most of the things felt homely but the first thing that caught my attention was, there no auto-complete feature available on the terminal for Git commands.

Git is the first step to start working on any project, so this small thing was what I wanted to fix on Mac. I asked few of my fellow Mac using friends but...

Read complete blog post

In the previous article, we have seen how to configure DigitalOcean Droplet. Now let's proceed further to set up our application repository and Ngnix with Phusion Passenger on the DigitalOcean droplet.

1. Install RVM and Ruby

We will install ruby using Ruby Version Manager(RVM) as it gives more flexibility to manage multiple ruby versions on the same system over rbenv, chruby, etc. Import RVM GPG key, before installing RVM:

gpg --keyserver hkp://keys.gnupg.net --recv-keys...

Read complete blog post

Git Aliases and set it up in UNIX

I have created a list of git aliases that can be used in our day to day work. Most of us might have configured this. But I have listed few more aliases that are normally not used. like 'ggr'

# Add and Removes
alias "ga"='git add'
alias "gai"='git add -i'
alias 'grm'='git rm'
alias 'gra'='git remote add'
alias "grr"='git remote rm'

# Commit and Pushes
alias "gcm"='git commit -m'
alias...

Read complete blog post

hub is a command line tool that wraps git in order to extend it with extra features and commands that make working with GitHub easier.

Install

$ gem install hub
$ hub hub standalone  ~/bin/hub && chmod +x ~/bin/hub

check successful installation with

 $hub version

Create a new github repo

 demo-project$ git create [NAME] [-p] [-d DESCRIPTION] [-h HOMEPAGE]

annotations

-p create a private repository

-d set the repository's description

-h set the homepage URL

This will create a...

Read complete blog post

Standards to follow while committing to Git:- what your commit message should tell

the diff says WHAT YOU DID;

your commit message should tell me or others in the team

WHY YOU DID THIS

Therefore, first and foremost add context (the why, not the how) with your commit message (e.g. "frobnize the message to enable persistence") instead of "added frob() function"). It's more effort (you have to reflect and think), but it is so much more worth.

Everyone these days working with one or the other Version controls systems and Agile tracking tools. Currently for our most of the project, we are working with github and for tracking we all are using Pivotal, Trello or some other tools.

Now these apps are having some cool apis and api tokens which helps us integrating Version control system and tracking tools. So that when we commit something that same message gets saved in our tracking tool. At the same time those tracking tools change...

Read complete blog post

Pretty often we are in situation where we need to merge branches especially while using "branch per feature" pattern to push our changes to repo.

You may follow these simple yet very important steps to merge your branches.

1) Assuming that you are on "master" branch on your local repo, do this to check the branch.

git branch

Expected output

master

2) Checkout the branch you want to merge, example you want to merge branch "feature-devise", So do this

git checkout feature-devise

Expected output...

Read complete blog post