GIT - 2

 Stages of GIT and its terminology

==================================


Git is DVCS. It is created by linus. It is software.

Github is a service. it is not git. It is like storage 

Gitlab is a service. it is not git. It is like storage 


stage of GIT/workflow

-----------------------

1. Workspace/working directory

2. Staging area

3. Local Repo


Repository:

==========

-> Repository is a place where you have all your codes or kind of folder on server.

-> It is a kind of folder related to one product.

-> Changes are personal to that particular Repository.


Server:

======

-> It stores all Repositories.

-> It contains metadata also.


Working Directory:

=================

-> Where you see files physically and do modification.

-> At a time, you can work on particular branch.


In other CVCS, develpers generally makes modificatons and commit there changes directly to the repository but git uses a different strategy. Git does not track each and every modified file whenever you do commit an operation. git looks for the files present int the staging area only those files present in the staging area are considered for commit and not all the modified files.


working directory --->add --> staging area -->commit--->Local repository---> GIT hub.


Commit -ID /Verison-ID/version

=============================

-> Reference to identity each change.

-> To identify who changed the file.


Tags

====

Tags assign a meaningful name with a specific version in the repository Once a Tag is created for a particular save even if you create a new commit, it will not be updated.


Snapshots

=========

->Represents some data of particular time.

-> It is always Incremental i.e. It stores the changes (appended data) only Not entire copy.


Commit

======

-> store changes in repository. You will get one commit-ID

-> It is 40 alpha-nueric characters.

-> it uses SHA-1 checksum concept.

-> Even if you change one dot, commit-id will get change.

-> it actually helps you to track the changes.

-> commit is also named as SHA1 hash.


Push

====

Push operations copies changes from a local repository server to a remote or central repo. This is used to stroe the changes permanently into the git repository.


Pull

===

Pull operation copies the changes from a remote repository to a local machine. The pull operation is used for synchronisation between two repo.


Branch

======

Product is same, so one respository but different task.

-> each task has one separate.

-> finally merges (code) all branches.

-> useful when you want to work parallely.

-> can create one branch on the basis of another branch.

-> changes are personal to that particular branch.

-> default branch is "Master"

-> File created in workspace will be visible in any of the branch workspace until you commit. Once you commit then that file belong to the particular branch.


Advantages of git

==================

-> free and open source

-> fast and small -> as most of the operations are performed locally, therefore it is fast.

-> security -> get uses a common cryptographic hash function called secure hash function (SHA1) to name and identify objects within its database.

-> No need of powerful hardware.

-> Easier Branching -> if we create a new branch, it will copy all the codes to the new branch.


Type of repositories

===================

Bare Repositories (central Repo)

-> store and share only

-> all central Repositories are bare repo.


Non- bare repositories (local repo)

-> where you can modify the files

-> all local repositories are non-bare repositories


Comments

Post a Comment

Popular posts from this blog

GIT - 3

 How to use git and create github account ========================================= AWS account-> create two EC2 instance (Linux) allow ssh and http port in security group. on first machine. ================ -> sudo su  -> yum upate -y -> yum install git -y -> git --version  or which git -> git config --global user.name "bhupinder" -> git config --global user.email "bhupinder@gmail.com" -> git config --list on second machine ================= -> sudo su  -> yum upate -y -> yum install git -y -> git --version  or which git -> git config --global user.name "Ajay" -> git config --global user.email "Ajay@gmail.com" -> git config --list
Read more

Docker - 6

 How to psuh docker image in dockerhub ===================================== Now go to putty -> Login as -> Sudo su -> yum update -y -> yum install docker -y -> service docker start -> docker run -it ubuntu /bin/bash Now create some files inside container Now create image of this container -> docker commit container1 image1 Now create account in hub.docker.com Now go to your server -> docker login -> enter your username and password Now give tag to your image -> docker tag image1 docker id/newimage -> docker push dockerid/newimage Now you can see this iamge in docker hub account Now create one instance in tokyo region and pull image from hub -> docker pull dockerid/newimage -> docker run -it --name mycon dockerid/newimage /bin/bash Some Important commands ===================== 1) Stop all running containers: docker stop $(docker ps -a -q) 2) Delete all stopped containers: - docker rm $(docker ps -a -q) 3) delete all images:- docker rmi -f $(do...
Read more

GIT - 1

 Introduction of GIT ==================== software configuration management   or source code management a) Centralised version control system b) Distributed version control system CVCS ---- drawbacks: --------- 1) It is not locally available, meaning you always need to be connected to a network to perform any action. 2) since everything is centralised, if central server gets failed, you will lose entire data. Eg- SVN tool. DVCS ---- In distributed version control system, every contributor has a local copy or 'clone' of the main repository. I.e. everyone maintains a local repository of their own which contains all the files and metadata present is Main repository. Difference between CVCS and DVCS CVCS ----- 1) In Cvcs, a client need to get local copy of source from server, do the changes and commit those changes to central source of server. 2) CVCS  system are easy to learn and setup. 3) working on braches is difficult in cvcs developer often  faces merge con...
Read more