yosemitebandit

$ ssh-keygen -l -f /path/to/keys/id_rsa.pub
2048 aa:bb:cc:dd:ee:ff:00:11:22:33:44:55:66:77:88:99 id_rsa.pub (RSA)

lolindrath

# View the log to find the commit you want to edit:
git log

# Quit out of the log
q

# Rebase from the commit you want to edit, in interactive mode:
git rebase SOME_COMMIT_ID^ --interactive

# This will open an interactive menu in Vi

syafiqfaiz

1. Change your database RDS instance security group to allow your machine to access it.
   • Add your ip to the security group to acces the instance via Postgres.
2. Make a copy of the database using pg_dump
   • $ pg_dump -h <public dns> -U <my username> -f <name of dump file .sql> <name of my database>
   • you will be asked for postgressql password.
   • a dump file(.sql) will be created
3. Restore that dump file to your local database.
   • but you might need to drop the database and create it first
   • $ psql -U <postgresql username> -d <database name> -f <dump file that you want to restore>

• the database is restored

amitpatelx

This page outlines about practices we are following related to development and deployment

Branches

1. Unless mentioned in issue or verbally, create all branches from develop branch.
2. Pull latest changes from the parent branch before creating a branch from it.
3. Branch name should be self-explanatory about the issue you are working on(Trello Card). It is highly discouraged to use an abbreviation, issue number etc in branch names.
4. Avoid creating nested branches from working branches. Do proper planning before start coding.

Naming the branch

1. All enhacements and feature branches should start with feature/ eg. feature/google-oauth-integration which will be created from develop only.