So I know we'll be talking about the.
So let me explain the server architecture in the architecture, the server goes down, you cannot access
to our files, so you are the client and the server will be in your organization or not outside of your
organization.
So you will be working on some project first and then what you want to do is use so those files in the
server.
So that's why in the previous order, less they help maintain this kinds of architecture.
But what if the server goes down?
Our server has crashed.
So then if you want to work at the temp, we cannot access our files now.
So if server carriers don't go further, then our files will get deleted.
So then we cannot access servers that say this version control systems came into the whole place in
Washington, two systems, you, your friends.
And so we had a project for us, not to mention here, but the members were working on a project, working
on a project.
So you said you can say if you have 10 members working on the project, you another 10 guys, then all
are these numbers will have a local copy.
And also the server will have a local copy of this project first.
And whenever you updated this project first, you can just use the comments to update on every.
We can update the Sahwa and other members there to pull the updated version from the Sahwa.
So even though the server crashes than your computer crashes, then you can ask your friends.
You can just on the project files from your other private members.
So this is very advantageous for the systems.
So in case the Iraqis don't, you can have a local copy and also you can run from your project with
our friends and multiple backups and reverting back to previous versions of the main when we are working
on the system.
So we have already seen multiple backups so that in case of any crashes, we can just have multiple
backups and also reverting back to previous versions.
So if you are testing an application and you think if the latest version how some problems are bugs,
then you can go back to the previous version.
And it is an example of the Russian control system.
And I need to tell you some some of these storms and this is these are called on.
Get up, get up and go.
So fast is when the first one is the top.
And this is where we can store our product first in the Verdasco repositories.
So the need to a new tool for these four repositories so these repositories can be added and updated
and pulled from this database.
So this is like Google or any groceries where we can store all product files so we can store any type
of any extension.
And this GitHub can be seen by any public user.
That means if you want to get up, then anyone can search your GitHub, provide them, or can you start
in Google and they can see your you know, if you do if you don't want this public and if you want to
start working on some private project, you can use the same getup, but for personal or private projects.
So if your team are working on some projects, you can set up these similar to the GitHub.
And next one is good, but this is more for documenting your information, so get book is like a digital
notebook and you can have those pages and pages.
You can read the content in modern architecture format.
So these are some very important and recently Microsoft has purchased the debt so we can create privilege
in a hospital, so previously we have to maintain public and private repositories.
So with the Microsoft purchasing, we can just recreate the private repositories in GitHub itself.
And I want to tell you these two topics, first were are tracking.
So this is where our project files, we decide if you have any files and you can add them to our tracking.
So this working there are.
I wrote the spelling mistake here.
OK, this one that we're tracking keeps track of the genius of these files.
You need to add your desired product files into this work and you can check the status of these files,
whether these are modified or not.
So if you think these are fit, you need to add those files to the staging area.
So the staging area is where our computer files are simply we want to sell state of the particular file.
So if you are more if you modify the file and you want to sue the state or the change, you need to
add the staging area.
So after adding the first staging area we can now push to the repository are created further.
So pushing to the positive means the files in the staging area will be sent to the our database.
Or are you just pushing to the top?
Sara.
So no proposal contains the first initiating, so the first initiating element updater in our.
OK, I think you have understood.
No, no, let me explain this again.
First, we have some product for a certain product first, and you need to add them to the work industry.
And then if you have changed, General, need a new file.
You need to add them to the staging area.
If you want to sell that state of that file and then you can push to the repository, are you going
further?
So you have two choices.
Either you can push through the policy or you can further and you can also revert back to these previous
versions using that, uh, comment.
So we are looking at that in the next video.
So these two other men for starting the first and working out and then committing them into the staging
area.
So.
Saving the face and committing the staging area is called committing and then pushing, the Russians
are pushing and then you're going to further.
So, uh, and there is one more thing I need to say.
That is pull pull means if you are working with another person.
Are you are working on so on and then if any other person has updated some files and then you don't
know, right, you you will have the local copy and then how to get that updated.
Well, product placement, you can pull those reports you can put out to pasture and put in that Wall
Street gives us the latest and updated out of that report.
So we don't worry if this confuses you when we are doing something practical, you will get clear.