Want to save your codes? The opensource version control system GIT could be your choice.
The following lines describe how to to setup Git on a Centos 6x (should work on RHEL, Fedora and other Linux distributions as well).
(The public IP address was marked as ""xx")
1. Install Git on the server and the Client:
# yum install git -y
2. Created a system user "git" on the server.
# useradd git
# sudo su - git
3. Generate a SSH keypair for the user "git" to facilitate "git" over SSH:
$ ssh-keygen -t rsa
Generating public/private rsa key pair.
Enter file in which to save the key (/home/git/.ssh/id_rsa):
Created directory '/home/git/.ssh'.
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /home/git/.ssh/id_rsa.
Your public key has been saved in /home/git/.ssh/id_rsa.pub.
The key fingerprint is:
8a:18:fd:72:37:c2:f9:a0:28:8a:f6:7d:51:98:56:a9 git@ins-1
The key's randomart image is:
+--[ RSA 2048]----+
| . |
| o |
| = |
| . E . |
| . . . S |
| o + + |
| . o O + |
|o. ..+ * . |
|=.o.... . |
+-----------------+
4. Copy the contents of the Public SSH key to the authorized_key file for the
user "git":
$ cat /home/git/.ssh/id_rsa.pub > /home/git/.ssh/authorized_keys
5. Copy the private SSH key to the local system (client) and store it in a file
under some directory; we would be using this key to connect with Git server (using "git" user).
6. On the server and the client change the permission of the authorized_key
and the private key to (0600), else it will complain while making SSH
connection;
A. Server:
chmod 0600 /home/git/.ssh/authorized_keys
B. Client:
# chmod 0600 id-rsa-private
7. Test a normal SSH connection from the client;
$ ssh -i id-rsa-private git@xxx.xxx.xx.xx
[git@ins-1 ~]$
So, the SSH connection is working!
8. Store the ssh private key in the Keychain so that you don't need to specify it
every time while making the SSH connection;
$ eval $(ssh-agent -s)
Agent pid 97010
$ ssh-add id-rsa-private
Identity added: id-rsa-private (id-rsa-private)
9. Create an empty Repository on the server:
A. Created a Project Directory:
$ mkdir Projects
$ cd Projects/
B. Under Project directory, created one emppty repository:
$ git init --bare project-1.git
Initialized empty Git repository in /home/git/Projects/project-1.git/
10. On the client let us clone this repository first;
A. Create a Local directory (if you wish)
$ mkdir Project-1-Local
$ cd Project-1-Local/
B. Set up and initialize the new repository on the client:
$ git init && git remote add origin
git@xxx.xxx.xx.xx:/home/git/Projects/project-1.git/
Initialized empty Git repository in /home/bijit/GIT-User/Project-1-
Local/.git/
This will set up the GIT environment locally, check using ls -al
***********************
$ ls -al
total 12
drwxrwxr-x. 3 bijit bijit 4096 Dec 9 13:43 .
drwxrwxr-x. 4 bijit bijit 4096 Dec 9 13:26 ..
drwxrwxr-x. 7 bijit bijit 4096 Dec 9 13:43 .git
***********************
**** For cloning the remote repo locally;
$ git clone git@xxx.xxx.x.x:/home/git/Projects/project-1.git
======================================
eg.
$ git clone git@192.168.1.4:/home/git/Projects/project-1.git Initialized empty Git repository in /home/centos/myProjects-Local/project-1/.git/ warning: You appear to have cloned an empty repository.
======================================
C. Do a git config to see the configurations:
$ cd project-1/
$ git config -l
core.repositoryformatversion=0
core.filemode=true
core.bare=false
core.logallrefupdates=true
remote.origin.url=git@xxx.xxx.xx.xx:/home/git/Projects/project-1.git/
remote.origin.fetch=+refs/heads/*:refs/remotes/origin/*
GIT PUSH:
11. Now, on the client create some test files and directories and push it to the
GIT server:
A.
$ pwd
/home/bijit/GIT-User/Project-1-Local
B. Create contents:
$ mkdir Test-Dir-1
$ echo "Test content" > test-file-1.txt
C. Add and Commit Locally:
$ git add .
$ git commit -m "Test commit 1"
[master (root-commit) 35aa811] Test commit 1
Committer: Bijit Bhattacharjee
Your name and email address were configured automatically based
on your username and hostname. Please check that they are accurate.
You can suppress this message by setting them explicitly:
git config --global user.name "Your Name"
git config --global user.email you@example.com
After doing this, you may fix the identity used for this commit with:
git commit --amend --reset-author
1 file changed, 1 insertion(+)
create mode 100644 test-file-1.txt
D. Push the contents to Remote GIT server:
$ git push origin master
Counting objects: 3, done.
Writing objects: 100% (3/3), 242 bytes | 0 bytes/s, done.
Total 3 (delta 0), reused 0 (delta 0)
To git@xxx.xxx.xx.xx:/home/git/Projects/project-1.git/
* [new branch] master -> master
GIT PULL:
1. Make a test directory and pull the contents from the remote Git Repo:
$ mkdir Test-Checkout-P1
$ cd Test-Checkout-P1/
2. Initialize the directory:
$ git init && git remote add origin
git@xxx.xxx.xx.xx:/home/git/Projects/project-1.git/
Initialized empty Git repository in /home/bijit/GIT-User/Test-Checkout-
P1/.git/
3. Now, pull the contents:
$ git pull origin master
From xxx.xxx.xx.xx:/home/git/Projects/project-1
* branch master -> FETCH_HEAD
[bijit@localhost Test-Checkout-P1]$ ll
total 8
-rw-rw-r--. 1 bijit bijit 6 Dec 9 15:50 file-2.txt
-rw-rw-r--. 1 bijit bijit 13 Dec 9 15:50 test-file-1.txt
Note: Did not pull the empty directory (Test-Dir-1) initially, but when that Directory was pushed with a file (file-1.txt). Subsequent pulls were able to bring down the Directory with its contents.
A. Create one branch locally say "bash", write a test script and Push the branch to remote repository;
1. $ pwd
/home/centos/myProjects-Local/project-1
2. Check all branches once
$ git branch -a
* master
remotes/origin/master
2. git branch bash
3. Switch to local branch "bash"
$ git checkout bash
Switched to branch 'bash'
4. Create a script and change permission;
$ vi hello.sh
$ chmod u+x hello.sh
5. Add the file locally;
$ git add hello.sh
$ git status
# On branch bash
# Changes to be committed:
# (use "git reset HEAD..." to unstage)
#
# new file: hello.sh
#
6. git commit -m "Added a script to new branch"
7. Push the branch;
$ git push origin bash
Counting objects: 4, done.
Compressing objects: 100% (2/2), done.
Writing objects: 100% (3/3), 345 bytes, done.
Total 3 (delta 0), reused 0 (delta 0)
To git@192.168.1.4:/home/git/Projects/project-1.git
* [new branch] bash -> bash
B. Checkout the remote branch and merge that branch to master;
1. Check local branch;
$ git branch -l
* bash
master
2. $ git checkout master
$ git checkout master
Switched to branch 'master'
3. $ git pull origin master
===================
$ git pull origin master
From 192.168.1.4:/home/git/Projects/project-1
* branch master -> FETCH_HEAD
Already up-to-date.
====================
4. Merge the branch eg. our branch is "bash"
$ git merge bash
=========================
$ git merge bash
Updating 2420bef..f8d2345
Fast-forward
hello.sh | 5 +++++
1 files changed, 5 insertions(+), 0 deletions(-)
create mode 100755 hello.sh
==========================
5. Push the changes;
$ git push origin master
===============================
$ git push origin master
Total 0 (delta 0), reused 0 (delta 0)
To git@192.168.1.4:/home/git/Projects/project-1.git
2420bef..f8d2345 master -> master
===============================
Accessing BitBucket using SSH keys, How-To
1. On the client system generate a ssh keypair to be used for git;
# ssh-keygen -t rsa
Generating public/private rsa key pair.
Enter file in which to save the key (/root/.ssh/id_rsa): /opt/bijit/others/.ssh-keys/bijit_bb
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /opt/bijit/others/.ssh-keys/bijit_bb.
Your public key has been saved in /opt/bijit/others/.ssh-keys/bijit_bb.pub.
The key fingerprint is:
ba:76:aa:d4:82:ca:32:fa:33:d1:c4:22:ea:81:d0:b0 root@ip-172-16-20-101
The key's randomart image is:
+--[ RSA 2048]----+
| |
|. |
| + . |
|E o o |
|+. + S |
|o..... . |
|. o.o o |
|+oo. .... |
|=+.o.ooo |
+-----------------+
2. Copy the contents of the public key (.eg bijit_bb.pub), and paste it in BitBucket project
under deployment keys section. [Thus, your key would now be identified]
# cat bijit_bb.pub
ssh-rsa
AAAAB3NzaC1yc2EAAAADAQABAAABAQDa4dHa3f51tl0H4Ye86qHxp4o6
VgRwhOIn4JZIArFMKwy9k5DqHFyKh38rvtM7weO2OUkgMZIyDMZL5LM67
wj+Wem1Baa4aF/DsV69Ns6deB7kGkGPg0HEbU8RrPTZkOaNdt8XjpADhjhkjhjk
hhj7CS5i6CXF02LJpe4ol6E0vbDyc6eufuUWlCTSqPf6FOaD+CGVaDuv9aCOEP10imt
O5t3e0BaD80jDi58mbZl7ZuNdDOOTP/N4JNGcEpAkooc7/9LaSnrc87eHI04Fah/7
i3dbu5DFG73dMCrRve3hOJuqwsvi80VU3vXiSGOpSjLQLrACKpmQK004Qdy
oUIqcv root@ip-172-16-20-101
3. On the client system, clone the project repo;
# git clone https://bijit@bitbucket.org/project-dir/project-repo-name.git
4. Add the ssh private key that you have geerated earlier (in either of the following two methods)
# ssh-agent bash -c 'ssh-add /opt/bijit/others/.ssh-keys/bijit_bb; cd /opt/bijit/others/repos/project-
name; git pull'
Or,
# eval $(ssh-agent -s)
Agent pid 3463
# ssh-add /opt/bijit/others/.ssh-keys/bijit_bb
Enter passphrase for /opt/bijit/others/.ssh-keys/bijit_bb:
Identity added: /opt/bijit/others/.ssh-keys/bijit_bb (/opt/bijit/others/.ssh-keys/bijit_bb)
# cd /opt/bijit/others/repos/project-name/
# git pull
Already up-to-date.
The following lines describe how to to setup Git on a Centos 6x (should work on RHEL, Fedora and other Linux distributions as well).
(The public IP address was marked as ""xx")
1. Install Git on the server and the Client:
# yum install git -y
2. Created a system user "git" on the server.
# useradd git
# sudo su - git
3. Generate a SSH keypair for the user "git" to facilitate "git" over SSH:
$ ssh-keygen -t rsa
Generating public/private rsa key pair.
Enter file in which to save the key (/home/git/.ssh/id_rsa):
Created directory '/home/git/.ssh'.
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /home/git/.ssh/id_rsa.
Your public key has been saved in /home/git/.ssh/id_rsa.pub.
The key fingerprint is:
8a:18:fd:72:37:c2:f9:a0:28:8a:f6:7d:51:98:56:a9 git@ins-1
The key's randomart image is:
+--[ RSA 2048]----+
| . |
| o |
| = |
| . E . |
| . . . S |
| o + + |
| . o O + |
|o. ..+ * . |
|=.o.... . |
+-----------------+
4. Copy the contents of the Public SSH key to the authorized_key file for the
user "git":
$ cat /home/git/.ssh/id_rsa.pub > /home/git/.ssh/authorized_keys
5. Copy the private SSH key to the local system (client) and store it in a file
under some directory; we would be using this key to connect with Git server (using "git" user).
6. On the server and the client change the permission of the authorized_key
and the private key to (0600), else it will complain while making SSH
connection;
A. Server:
chmod 0600 /home/git/.ssh/authorized_keys
B. Client:
# chmod 0600 id-rsa-private
7. Test a normal SSH connection from the client;
$ ssh -i id-rsa-private git@xxx.xxx.xx.xx
[git@ins-1 ~]$
So, the SSH connection is working!
8. Store the ssh private key in the Keychain so that you don't need to specify it
every time while making the SSH connection;
$ eval $(ssh-agent -s)
Agent pid 97010
$ ssh-add id-rsa-private
Identity added: id-rsa-private (id-rsa-private)
9. Create an empty Repository on the server:
A. Created a Project Directory:
$ mkdir Projects
$ cd Projects/
B. Under Project directory, created one emppty repository:
$ git init --bare project-1.git
Initialized empty Git repository in /home/git/Projects/project-1.git/
10. On the client let us clone this repository first;
A. Create a Local directory (if you wish)
$ mkdir Project-1-Local
$ cd Project-1-Local/
B. Set up and initialize the new repository on the client:
$ git init && git remote add origin
git@xxx.xxx.xx.xx:/home/git/Projects/project-1.git/
Initialized empty Git repository in /home/bijit/GIT-User/Project-1-
Local/.git/
This will set up the GIT environment locally, check using ls -al
***********************
$ ls -al
total 12
drwxrwxr-x. 3 bijit bijit 4096 Dec 9 13:43 .
drwxrwxr-x. 4 bijit bijit 4096 Dec 9 13:26 ..
drwxrwxr-x. 7 bijit bijit 4096 Dec 9 13:43 .git
***********************
**** For cloning the remote repo locally;
$ git clone git@xxx.xxx.x.x:/home/git/Projects/project-1.git
======================================
eg.
$ git clone git@192.168.1.4:/home/git/Projects/project-1.git Initialized empty Git repository in /home/centos/myProjects-Local/project-1/.git/ warning: You appear to have cloned an empty repository.
======================================
C. Do a git config to see the configurations:
$ cd project-1/
$ git config -l
core.repositoryformatversion=0
core.filemode=true
core.bare=false
core.logallrefupdates=true
remote.origin.url=git@xxx.xxx.xx.xx:/home/git/Projects/project-1.git/
remote.origin.fetch=+refs/heads/*:refs/remotes/origin/*
GIT PUSH:
11. Now, on the client create some test files and directories and push it to the
GIT server:
A.
$ pwd
/home/bijit/GIT-User/Project-1-Local
B. Create contents:
$ mkdir Test-Dir-1
$ echo "Test content" > test-file-1.txt
C. Add and Commit Locally:
$ git add .
$ git commit -m "Test commit 1"
[master (root-commit) 35aa811] Test commit 1
Committer: Bijit Bhattacharjee
Your name and email address were configured automatically based
on your username and hostname. Please check that they are accurate.
You can suppress this message by setting them explicitly:
git config --global user.name "Your Name"
git config --global user.email you@example.com
After doing this, you may fix the identity used for this commit with:
git commit --amend --reset-author
1 file changed, 1 insertion(+)
create mode 100644 test-file-1.txt
D. Push the contents to Remote GIT server:
$ git push origin master
Counting objects: 3, done.
Writing objects: 100% (3/3), 242 bytes | 0 bytes/s, done.
Total 3 (delta 0), reused 0 (delta 0)
To git@xxx.xxx.xx.xx:/home/git/Projects/project-1.git/
* [new branch] master -> master
GIT PULL:
1. Make a test directory and pull the contents from the remote Git Repo:
$ mkdir Test-Checkout-P1
$ cd Test-Checkout-P1/
2. Initialize the directory:
$ git init && git remote add origin
git@xxx.xxx.xx.xx:/home/git/Projects/project-1.git/
Initialized empty Git repository in /home/bijit/GIT-User/Test-Checkout-
P1/.git/
3. Now, pull the contents:
$ git pull origin master
From xxx.xxx.xx.xx:/home/git/Projects/project-1
* branch master -> FETCH_HEAD
[bijit@localhost Test-Checkout-P1]$ ll
total 8
-rw-rw-r--. 1 bijit bijit 6 Dec 9 15:50 file-2.txt
-rw-rw-r--. 1 bijit bijit 13 Dec 9 15:50 test-file-1.txt
Note: Did not pull the empty directory (Test-Dir-1) initially, but when that Directory was pushed with a file (file-1.txt). Subsequent pulls were able to bring down the Directory with its contents.
A. Create one branch locally say "bash", write a test script and Push the branch to remote repository;
1. $ pwd
/home/centos/myProjects-Local/project-1
2. Check all branches once
$ git branch -a
* master
remotes/origin/master
2. git branch bash
3. Switch to local branch "bash"
$ git checkout bash
Switched to branch 'bash'
4. Create a script and change permission;
$ vi hello.sh
$ chmod u+x hello.sh
5. Add the file locally;
$ git add hello.sh
$ git status
# On branch bash
# Changes to be committed:
# (use "git reset HEAD
#
# new file: hello.sh
#
6. git commit -m "Added a script to new branch"
7. Push the branch;
$ git push origin bash
Counting objects: 4, done.
Compressing objects: 100% (2/2), done.
Writing objects: 100% (3/3), 345 bytes, done.
Total 3 (delta 0), reused 0 (delta 0)
To git@192.168.1.4:/home/git/Projects/project-1.git
* [new branch] bash -> bash
B. Checkout the remote branch and merge that branch to master;
1. Check local branch;
$ git branch -l
* bash
master
2. $ git checkout master
$ git checkout master
Switched to branch 'master'
3. $ git pull origin master
===================
$ git pull origin master
From 192.168.1.4:/home/git/Projects/project-1
* branch master -> FETCH_HEAD
Already up-to-date.
====================
4. Merge the branch eg. our branch is "bash"
$ git merge bash
=========================
$ git merge bash
Updating 2420bef..f8d2345
Fast-forward
hello.sh | 5 +++++
1 files changed, 5 insertions(+), 0 deletions(-)
create mode 100755 hello.sh
==========================
5. Push the changes;
$ git push origin master
===============================
$ git push origin master
Total 0 (delta 0), reused 0 (delta 0)
To git@192.168.1.4:/home/git/Projects/project-1.git
2420bef..f8d2345 master -> master
===============================
Accessing BitBucket using SSH keys, How-To
1. On the client system generate a ssh keypair to be used for git;
# ssh-keygen -t rsa
Generating public/private rsa key pair.
Enter file in which to save the key (/root/.ssh/id_rsa): /opt/bijit/others/.ssh-keys/bijit_bb
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /opt/bijit/others/.ssh-keys/bijit_bb.
Your public key has been saved in /opt/bijit/others/.ssh-keys/bijit_bb.pub.
The key fingerprint is:
ba:76:aa:d4:82:ca:32:fa:33:d1:c4:22:ea:81:d0:b0 root@ip-172-16-20-101
The key's randomart image is:
+--[ RSA 2048]----+
| |
|. |
| + . |
|E o o |
|+. + S |
|o..... . |
|. o.o o |
|+oo. .... |
|=+.o.ooo |
+-----------------+
2. Copy the contents of the public key (.eg bijit_bb.pub), and paste it in BitBucket project
under deployment keys section. [Thus, your key would now be identified]
# cat bijit_bb.pub
ssh-rsa
AAAAB3NzaC1yc2EAAAADAQABAAABAQDa4dHa3f51tl0H4Ye86qHxp4o6
VgRwhOIn4JZIArFMKwy9k5DqHFyKh38rvtM7weO2OUkgMZIyDMZL5LM67
wj+Wem1Baa4aF/DsV69Ns6deB7kGkGPg0HEbU8RrPTZkOaNdt8XjpADhjhkjhjk
hhj7CS5i6CXF02LJpe4ol6E0vbDyc6eufuUWlCTSqPf6FOaD+CGVaDuv9aCOEP10imt
O5t3e0BaD80jDi58mbZl7ZuNdDOOTP/N4JNGcEpAkooc7/9LaSnrc87eHI04Fah/7
i3dbu5DFG73dMCrRve3hOJuqwsvi80VU3vXiSGOpSjLQLrACKpmQK004Qdy
oUIqcv root@ip-172-16-20-101
3. On the client system, clone the project repo;
# git clone https://bijit@bitbucket.org/project-dir/project-repo-name.git
4. Add the ssh private key that you have geerated earlier (in either of the following two methods)
# ssh-agent bash -c 'ssh-add /opt/bijit/others/.ssh-keys/bijit_bb; cd /opt/bijit/others/repos/project-
name; git pull'
Or,
# eval $(ssh-agent -s)
Agent pid 3463
# ssh-add /opt/bijit/others/.ssh-keys/bijit_bb
Enter passphrase for /opt/bijit/others/.ssh-keys/bijit_bb:
Identity added: /opt/bijit/others/.ssh-keys/bijit_bb (/opt/bijit/others/.ssh-keys/bijit_bb)
# cd /opt/bijit/others/repos/project-name/
# git pull
Already up-to-date.
