Hello everyone, to see emerging software advancement in the IT corporate world and due to their trending IT infrastructure. So, today in this article, we are going to give lessons on the installation process of Jira on Mac Os so, we will look at prerequisites and then we will download Jira for Mac Os, how to start and shutdown Jira (Tomcat), set up the home directory and then finally, we will set up Jira for use. Let’s have a look!

Let us begin.

Step 1:

Prerequisites for installing Jira on the mac operating system

Java must be installed in your system so to check you can go to your terminal and say java –version and this shows you your java version currently installed in case you are not getting this you can install java first and then if you will have this prerequisite completed step number two will be

Step 2:

How to download Jira for Mac OS

You will download Jira for the mac operating system and this is the site

https://www.atlassian.com/software/jira/download

Where you will download it from so you will go to google and you can say download Jira and you will get that site, you will go there and there you will get that information it is free for thirty days for unlimited users and there you can select your operating system so, you will select OS 10 and then download so it will take a few seconds to a few minutes to download so you have already downloaded it if you will go to your downloaded zip file so if you will go to your downloads folder you will see that zip file which will get downloaded and you will unzip this so, you will have unzipped it and kept on your desktop there so this will be unzipped folder so now the third step is

Step 3:

How to start and shutdown Jira

Or you can also say the Jira tomcat server because Jira comes with the tomcat server so you will have to go to the bin directory inside the folder and you will find startup.SH and shutdown got SH files and these are the files that you will run to start and shutdown Jira server so, we will learn that you will go inside your folder and there you will see there will be bin directory and inside the bin, you will find that startup.SH and shut down. SH there you will have a startup.SH and there you will have a shutdown.SH so, to start you will go to the terminal and go to the location bin folder so for example, you will just press command on your keyboard to get that information and copy the location of that folder and then you will go to your terminal and you will change the directory to that bin folder of Jira and now you can say SH startup.SH and hit enter and you will see that information and it would show you tom get started and to check you can go to your browser and you can go to localhost 8080 so as of now it will not run or you may run this command again and yes, you will see the Jira server is up but there will some problem and it will say we cannot locate the Jira home directory so you will have to set up the home directory so what you will do you will shut it down so you will say sh shutdown.SH and tomcat will stop so if you go to localhost 8080 now so you will see the server will be stopped and you will learn how to set up the home directory and that you have already seen that you will go to localhost 8080.

Step 4:

How to set home directory

To check if the Jira has server is running and to set the home directory you will have to go to that file Jira application. Properties which is inside web-inf glasses folder and  

Go to file Jira-application .properties located in Jira folder >> Atlassian–Jira >> Web-INF>> classes

there you will have to provide a location for Jira home so you will see how to do that so you will go to the Jira folder and you will have to go to atlassian Jira folder there you will have web-inf and there you will have classes and there you would find a file Jira application properties so you can open that file with any text editor on your system if you have a text wrangler, you will open this and you will see it will ask for your location for Jira home so you can create any folder and then provide that folder as Jira home so you will create a folder on your desktop itself and you will name that folder as Jira Home hit enter and just press command I to copy its location and you will give the same location on that file, you will give that location so that will Jira home and you can save it and close it okay and see you if you will open this folder as of now that will empty but as you will now start your Jira servers you will see there are folders and files getting created there all the logs will get there as well so now you will go back to your terminal and again say SH startup.asset and it’s storm get started you will go to your browser localhost 8080 you will run the start command again and you will go to localhost 8080 and now you will see atlassian Jira is starting up so it means it will take up your home directory as well it might take a few seconds to start up also if you will now go to your Jira home folder you will inside the folder and you can see all these logs and all these information will now getting created inside that folder. Now, for the first time, it will have this information if you want to set it up yourself or you want to set it up for me so, this is our next step.

Step 5:

Setup Jira for use

You will have to set up Jira for use so you will have started your Jira server and now you will complete the setup so you can click on set it up for me and continue there you will have to select the product so you will select Jira software and select Jira software server you can name any organization there up and running and then generate license so there it will give you the information of your license you will say yes confirmation and there it will ask you for some email ids and then password and retype the password so you will give some email id there and password say next so now it will finally set up all the instances and everything that Jira requires on that particular machine so you will wait for few seconds for that setup to get completed meantime you will look at some tips so instead of localhost you can also use the IP 127.0.0.1 which is the Ip for localhost or you can also use your system public IP instead of localhost so instead of localhost there you can use that IP and you will now see the Jira will ready to go and you can get started with Jira. I hope this information will be helpful for you and it will give you privileges as an onboarding learning concept with valuable steps.

Related video:  

Hello everyone, you know the different phases of programming and about its evaluation on that, it is performing their task. So, we are going to learn about Gitlab CI/CD from very basic & scratch and if you don’t have primer knowledge on the above topic so, don’t worry, we will go up step by step. And in this lesson, we will engage with various topics like what is Gitlab CI/CD? We will create a .gitlab-ci.yml file, this is a file where we add our jobs and create a pipeline and I will show you how to do that then we will run CI/CD pipeline in Gitlab so, this is going to be very easy and interesting.

What is Gitlab CI/CD?

Let us learn about what is Gitlab CI/CD? So, you will go to Google & search for continuous integration and delivery. You will go to images and select one image there. You will see there, you will have continuous integration then CI stands for continuous integration so, the continuous delivery is CD and again, we will call continuous deployment is CD so, this is what we call CI/CD. And there, if you will look at continuous integration. There will be a process where you will have these three jobs and processes, chained and linked with each other. Why is it will be linked? I mean, if the first dev process or dev job runs and passes. And it will trigger the next job that is in the test job application test. If the passes it will trigger then the next job that is an integration test and you will have our continuous integration pipeline completed so this is what is called as CI or continuous integration and if this all these jobs in this cycle are chained with each other and our automated triggered we call it as a continuous integration system now if you also add an acceptance test job or acceptance test process which is also automated and linked this becomes a continuous delivery because after this step our application or our product will be ready for delivery so this becomes continuous delivery and if we also add our deployment job or a deployment process that will reply to the production and all these jobs are automated and chained and can be automatically triggered then this becomes a continuous deployment pipeline so this is what we call as continuous integration and continuous delivery and continuous deployment. Now, in GitLab as well we have this corners integration delivery and deployment, and here this GitLab CI is an open-source CI service or a continuous integration service included with GitLab and by default, this is integrated with every in your GitLab since version 8.0 so, if you are using version 8.0 or above GitLab then in all your projects by default you will have GitLab CI integrated and enabled by default and to go to the settings and to configure GitLab CI you should be a maintainer or our owner or an admin on your project so, you go to your GitLab account if you just go to your Gitlab you will sign in so, you can see there your projects and if you see the projects there you will be maintainer on one projects and owner on the other projects so, you can configure GitLab CI/CD so, this is what GitLab CI/CD is now.

Create .gitlab-ci.yml file

Actually, create a GitLab CI/CD pipeline, you will have to add a file called .gitlab –ci.yml so, yml files or ml is a format of writing text files, and like you have JSON and XML. Ml is also a format and I will show you that how to create it and you have to create this file in the root folder of your project or your repository so, whatever the root folder is and you will be creating this file in the main folder or the root folder of your project. Now, before we start creating this file so, this is used to configure our pipelines and in every project, you will be having, you will be adding this file where you can add the details and it will define the structure and order of the pipeline and once you create it you will know exactly what you mean do not worry if there is there are some things that you are not getting once you create the file and run it you will know exactly what it means? So, you will create a file now if you are on Mac, you can use any text editors like you have text editors on Mac then you have text wrangler anything will work if you are on windows, you can again use notepad or notepad ++ or in fact, you can use any editor but you have to make sure the syntax is correct and I will show you how you can check the syntax so, you will open your window with notepad++. You will open a new file and on your mac, you will open your text wrangler file so that you can create it there so to create a file you will just give some name of the job you will say that is demo job one. So, you will say demo job one any name you can give there and give a colon go to the next line and you will give five spaces so, you can give any number of spaces but you will have to be consistent with that so now you will say tags and there give a colon again go the next line give two spaces and you will give a hyphen and spaces and I can give any tag here now tags are important because in your gitlab you will be having the gitlab runners and they have some tags and the text should match only then the gitlab runner will run this particular file so if you go to my project on gitlab and there if you go to settings and go to CI/CD and you have runners there you will click on expand and you can see you had created this runner earlier and you had given this these tags there CI and SSS so you should be having one of these tags so that the runner can pick up this file and run it so, you will say CI there and you will go again to next line now again you will give there script and this is in line with tags again go to next line two spaces – and there you can write any command or script you want to run so, you will say hello echo hello world so they should run this command in this job this is a very simple file where you are running that script echo hello world so they should print hello world on the console and now you can also do the same thing on your windows on the notepad so you can create it like this and now you will have to make sure the syntax is correct and for that you can copy the contents and you can just go to google and search for any ml file validator utility or application and you will see that you have yam lint, yaml validator online this all you will go to yaml lint and paste your contents of the ml file and there you have to go button you will click there go and check and yes everything is fine it will says it is a valid YAML so that is fine you will now just save this so you will save this file and you have to make sure the name there should be .gitlab –ci.yml as of now you will save on desktop but you will move it to your project folder so, you will say as it is. I hope this will more authenticate your performances and give you a hike in the sections of Gitlab CI/CD.

Related video:

Hello friends, today, we are going to teach you about Gitlab runner. On that how can you install, register, start Gitlab runner and we will do this on the Windows operating system (Windows OS). So, if you want to learn Gitlab runner then we will start from very basic it means from scratch and we will go up step by step.

What is Gitlab runner?

Before, I write down the steps to all procedure that happens in Gitlab runner. Let us see, what is Gitlab runner? So, in the very simple word if you talk about Gitlab CI. It is an open-source continuous integration service included with Gitlab. So, this service by default is included with Gitlab. It is used to run jobs & send results back to Gitlab.    

How to install Gitlab runner?

So, you will go to your Google and search for Gitlab runner. There will be a documentation page and you will go there. You will see all the documentation about Gitlab runner there so, it is written in a go programming language. And you may see all the features will be there, it will allow multiple jobs concurrently & compatibility. Then you will have a section for installing Gitlab runner and have an installed link. If you will see that there will be a link for Gitlab runner from there, you may install it. And you have lots of binaries over there so, you will go on windows. You will go to your window system and go to the same link. So, you will have the instructions for installation. You will create a folder in the name Gitlab-runner and you will choose from your C drive option, create a folder in the name of that. And the next step, you will have to download the binary for your operating system. You will go to your computer and this pc option and do a right-click, you will go to properties option. And you can see all details about your operating system, the bit size & everything. So, you will choose the bit size and download the Gitlab runner .exe. If you will go to your download folder then it will be there. You will copy that from there & move it to the folder Gitlab runner that will have been created. You will paste in that and rename it. If you will go to the documentation page so, there will be mentioned to take the rename the binary to Gitlab runner. Then you will have to run an elevated command prompt for this. Now, what does it mean? It means that you can run your command line with admin rights. And you can also use Git bash there, you will just move to your command line and from there, you will choose run as administrator option. From there, you will go to the location of that folder. Suppose, you will have in other drives like e drive then first, you will have to change the drive-by saying or writing e: and enter then you can go to the location. Also, the shortcut is you can go to the address bar of your folder and you will say cmd, press enter. Then it will open in the same folder, this is the shortcut so, you can do it. In your folder, you will have to run the command GitLab runner .exe install. So, you will run this command in administrator then you will see that it is done. If you will say GitLab runner –version then you will get all details there. So, these are the commands:-

Gitlab runner .exe install

Gitlab runner –version

To check, if your GitLab runner is installed so, you can run the command gitlab runner –version. Then you can also start using this command GitLab runner .exe start.

How to register Gitlab runner?

Now, you need to register your GitLab runner. If you will go to the GitLab documentation page then you will have the link to register GitLab runner. If you will scroll down, you will see that multiple operating systems and documentation for that. Further, you will scroll down, you will have windows. There will be steps that you can use for windows. So, you will first run GitLab runner .exe stop to stop the runner and for registration, you will have to run the command GitLab runner .exe register then you will do the registration process. So, it will ask for GitLab coordinator-ci URL and after entering the URL. Then it will ask for a GitLab-ci token so, the token you will get from your projects. You will log in to your GitLab account and will go to your projects, you can also go to your projects from the top bar. Then in your projects, you will go to settings. Under settings, you will go to CI/CD and there you will find sections of the runner. You will see sections for setup runner manually, there you will also see those steps you will have already done and the token will be there. After providing the token, you will have to provide some description like my-runner1 and anything you can say here. And it will also ask for GitLab-ci tags then you can add like ssh, ci, etc. If you will enter then it will show register runner …..Succeeded and everything will be done. Then it will ask to enter the executor like ssh, Kubernetes, custom, virtual box, Docker machine, etc. Then you will put shell and press enter so, it will show the runner registered successfully. So, you will start the runner using the command like gitLab runner .exe start  

How to start Gitlab runner?

Now, you will have to check. To start the Gitlab runner, the gitLab runner .exe start is the command to check. Then you will have to check if the runner is started and the next step will be to check runner is started in the project. The same thing, you will have to do for this. You will go to your projects then settings and after CI/CD. Again, you will go to runner and scroll down. If you will scroll down, you would see the project is activated under the runner. You will also see the name that you had given to that. Now, this runner will be activated and it can run the jobs. All this, you will have learned how to run jobs, use tags, and Gitlab ci. I hope, this data will be very helpful for you.

Related Video:

Hello-tech lover, welcome to the visualizing path of programming. You know better today trends to take up-gradation in technologies and their environment around the world. Through this article, we are going to give you lessons on Gitlab runner and we will go very basic step by step and learn how to install, register, and start Gitlab runner. So, if you have no primary knowledge of that then do not worry. We will start from scratch.

What is a Gitlab runner?

Gitlab runner is used in Gitlab CI and you have not learnt yet Gitlab CI. Now, this is an open-source continuous integration service. It is included with Gitlab, is used to run jobs & send results back to Gitlab. Now, let’s see, what are the steps you have to do for setting up Gitlab runner.

How to install Gitlab runner?

Let us see, what we will do about this? You will go to Google and search for Gitlab runner. You will visit the website for Gitlab runner documentation and you will see all the documents over there. This is written in a go programming language, you can see some features like multiple jobs concurrently run. And if you will have to move down, there will be a section of install Gitlab runner. You would find every sort of documentations about Gitlab runner like how to configure, troubleshooting, etc. If you will click on the install option then there will be options like Mac for the operating system. So, you will click on the option to install Mac operating system and there you will have the steps if you want to install it manually. Then you will have to install the binary in your system and you can use that given command from there. You may copy and run it in your terminal then it will download the binary. So, you will have to give permissions from the given command. This is the first way, the second way is homebrew installation. If you will go for homebrew, there will be a website so, you will see there “the missing package manager for Mac OS” like this type of thing will be written there. To install homebrew, it is very simple so, you will have to copy that statement from there and will have to run on terminal. Then you can start using homebrew, it is a good way to install and manage packages on Mac. There will be a command so, you will have to run that on your terminal then this will install Gitlab runner on your Mac operating system. Here are some commands to install, version, start, and stop like

Brew install Gitlab –runner

Gitlab-runner –version

Brew services start GitLab –runner

Brew services stop GitLab –runner

How to register Gitlab runner?

Let us see how can we register GitLab runner? So, there you will visit the Gitlab runner documentation. You will find the registration part in that you will have a register link and from there, you would see that what are the step to register the Gitlab runner? Now, on that page, if you will scroll down then you will find all the steps for Mac OS, window OS, etc. so, you will have to run the following command Gitlab –runner register, this is the first command. You will go to your terminal and run the command Gitlab –runner register then there, they shall ask for a Gitlab-ci token for this runner. So, to get the ci token, you will log in to your Gitlab account and you will have to take tokens from Gitlab projects. You will go to your project by doing a sign-in process then you would have to go to project settings. If you will see, scroll down and you will find the setting there. If you will go to settings under that you will get CI /CD section. You will go to CI/CD then you will have a section of runner then you will expand it. You will find the setup runner manually option will be there and there will be a token of your project. You will have to do copy that from there and provide it on the terminal and you will also put tags for your Gitlab ci like ssh, ci. Then you will see registering runner…..succeeded and after this, you will have to enter the name of executors like parallels, custom, Docker-ssh, etc. you have so many executors if you want to run on Docker and some Kubernetes. If you will put simple executor shell and press enter button. Then it will show the runner registered successfully. These are the commands which you have followed.

How to start Gitlab runner?

So, if you have to start Gitlab runner then you can use these brew services start Gitlab –runner. To start Gitlab runner, if you’re not using brew then you will have all the options there like Gitlab –runner stop. You can take Gitlab –runner start if you are not using brew. Then it will be successfully started and the next step will be to check runner is activated in the project. So, you will have to check runner is activated or not, again, you will go to your Gitlab, project, and in settings CI/CD. And there you will expand the runner section, if you will scroll down then you will see your runner will be there, it is started. You can also see the name and text that you had added. So, you have seen that how to use the runner and how to do Gitlab ci? I wish, these lessons will be very helpful for you.

Related video:

Hello my folks, welcome to the fascinating world of Gitlab. Nowadays, this has become a real use of every programmer/developer. You know every programmer needs some space to situate their projects and code which have been made by them. Today, in this Gitlab mainstream, we are going to elaborate on the SSH key in this you will learn about the fact of how can you create, manage with the SSH key.

What is an SSH key?

Let’s get started with SSH. SSH stands for secured shell and now, comes to the place of uses what is the use? This is used for authentication, by setting SSH you can connect to the Gitlab server without using a username and password each time. Once, you will set the SSH key so, you may skip using your username and password each time to connect your Gitlab server.

How to set up an SSH key in Gitlab?

Let see, what will have to do here?

Step 1: Run command SSH- keygen

You will have to run this command. If you are on MacBook, you can put terminal and will run the command SSH-keygen. You may enter the location or file where you have to save the key and press the enter key. So, you will have your ssh key created. This was on mac.

On mac. – run command on terminal

On windows – use putty or Git bash

If you are on windows then you can use an application or a client called putty, it is ssh client that you can use on windows or you can also use Git bash to run the command. If you will have installed it before, you will go to your windows system and search for Git bash. And you will adjust fonts if you will need them. So, you will run $ ssh-keygen then it will ask you to enter the file do you want to save it then again, you will press the enter so, it will have been created. You will go to your folder from local disk to .ssh in that two files will be created in the id_rsa and id_rsa.pub

Now, step no.2 will be

Step 2: log in to Gitlab account

                        Go to an account >> Settings >> SSH keys

So, you will go to your Gitlab and log in. you will sign in to your account if you will go to your account or profile at the top right. You would find settings there and if you will go in that. So, you will find an option for SSH key then you will click on that. You would add the content of your file id_rsa.pub. If you will go to the file and open it with any text editor like notepad and notepad++, you can copy the entire thing from there. And you will paste it to the SSH key. Suppose, you want to give a name to your key then you can add that name in the title option and switch to add key. So, you will see that everything would be edited there. There would be a key that you can use to authenticate and log in to the Gitlab server.

Now, here step no.3 is

Step 3: copy contents of id_rsa.pub and add key

Step 4: verify SSh key is added

 You have been seen. This is how you can add an SSH key to your Gitlab. I wish this all will be very useful for you.

Related video:

Hello folks, if you have a concept and skills on the git command so, that’s very great otherwise, you could pave your way in the glorious field of programming. Welcome to the admiring world of command that makes your way easy with day-to-day enhances which supports very in your life. This command could create turbulence in your daily workflow with innumerable enormous modes. With one command structure, you could conquer all your miseries over the git commands.

Push code to the remote repository

Suppose, you have a file in that you have done everything and you have to upload that all files on GitHub. So, open your GitHub, if you have your own GitHub account then you will log in to that. After the opening of your account, there will be the repository option. So, clicking on the new option, you will have to take create a new repository in the name all about git. Then you will give a description like this is git status one video repository so, after doing the public option you can create a repository. You can do public or private, whatever you want, there is no issue with that. You will see that there will show something command to you. Suppose, you have files in the name node integration so, which you have files in the node integration. First, you will have to take merge from node integration to the main branch then what will you do for that? You will do checkout in master by putting $ git checkout master. After that, you will put like $ git merge node integration, if you will write node and press tab then it will give to write whole. You will see, your branches will have been merged there. If you will visit vs code then node has also come in master. You could directly upload all files from vs code through the command line, how can you do that? First, you will have to take commit by putting $ git commit –m “All files done ready to upload” and after the commit, you will see git status by putting $ git status. You will have to take copy the command from GitHub and paste it into the command line. If you will have to do push so, you will see one thing over there, you could do two or three things. You have been seen everything how does it make? You have a remote repository that exists on the server. You have all files in the file explorer that you have to upload in it. So, you will put $ git remote then it will show you that it exists on the origin. When you will put $ git remote v then it will show you from where it will do fetch or push, it means you are fetching those files and uploading them on the server. Again, you will run a command for push like $ git origin master so, it will take time in demanding id & password then it will have happened push. When you will see fetching into GitHub and refresh that. Every committed file will be present there when you have committed and created it. You can see commits from there, when you will click on your name then every commit has been uploaded there. This is real benefits reach to our GitHub through the command line.

Clone a project command

Suppose, you have to do a clone, any repository is there. First, you will have to go home, in the name js project repository. You have opened any basic project from there and you have to clone that so, you will move in the code & copy that. So, you have an online js repository that somebody has made, you have to do clone and download it to your system. Then you will have to make a file on the desktop. Suppose, you have made a file in the name clone GitHub so, you will open GIT bash in that. Then you will put $ git clone and after, you will put copied URL with js project that you have done before. So, it will have to give clone, download, and receive. If you will see into GitHub then in the name js project file has been made. When every process will have done so, every file will have come. This is the real meaning of clone, any project exists on GitHub. So, you can directly clone in any repository. You will see that every file has come in the file explorer which another person had uploaded in their own project. Usually, you can do a clone, and anybody of project you can do. Those have a public project, you can do a clone of that. You can give an open-source contribution to that. So, you will use only GitHub because it is very reliable which is from Microsoft and it has seamless services.

Related video:

Hello techno-friendly users, welcome to the featuring era of programming. Today, we shall raise our points on the topic of branching and how directly you can establish your branch through the git command line without opening the GitHub platform. If you will also unaware to take git branching so, you have difficulties in relation to command branching then you can receive every kind of solution related to creating, merging, and adding branches. This is the place where you could get all steps regarding branch creations.

Creating branch from the command line

Suppose, you have to make a branch so, let’s have a look that what is branch happening? If you have software and you are working in google and that Google is working in a master branch, all files are running there. Suppose, you want to add a feature in the file but you are not so sure to talking that your boss will give you permission or not. If you do in the main file that will be affected on your main server, the file has become loose then your server will be shut down. So, here comes the talk of the branch, you will make a copy, the branch means making copies of the same file. Then first, you will write git status so, it will show on branch master, nothing to commit. When you will put $ git branch then it will show you in the master branch, if you have to make a branch so, you will put $ git branch update code then update code is branch name happen. So, again, you will run the $ git branch, there will be branches as master and update code that you have been made. If you have to do the switch in the update code so, you will have to put like $ git checkout update code then it will show you switched to branch ‘update code’ option. If you will move in the vs code file, you will do enhances in one then there will not be affected another file. Suppose, you have a file in the name contact.html, you have to write anything in that. You have been made a file in the name comment.html, you have paste similar code of your file and changed something code in that. If you will run git status then it will show you unstaged, when you will do commit through $ git commit –a –m “this update code files updated”. You will do update put anything message so, again, you will run git status then it will show you untracked files. Then you will first add that by putting $ git add –A when you will run git status, it will show you on branch update code nothing to commit, working tree clean. When you will do switch to the master branch then you will see what will happen with comment.html so, you will have to see two branches that you had made by putting $ git branch.

Merging two branch command

You had made a file in the name comment.html then it will happen in the update code branch. So, again, you will switch by putting $ git checkout master then they will have switched to branch ‘master’. When you will move to the vs code so, the comment.html file will not be there and also not visible in the file explorer because you had not that file in the master branch and you are updating that file in the update code. Again, you will do a checkout to update the code so, that the comment.html file will retrieve again in the vs code. This is the real meaning of branch, you can do switch, comment set up, add features also, and anything you want to do. Differently, you can make replicas of the project doing adding features in that, and after, you can merge them. Now, look at how can you do merge, what is merge means? Suppose, you have a project in the name comment.html in vs code, you have made that. You had made features in that boss has liked most, if they say that you have to give merge that with the master branch so, git has to give it directly. How does it do? So, what will be the command? First, you will see the git log by putting the $ git log then you will see files that will have been committed to those files you have done. By pressing Q, you have to give quit, first, you will have to move master. In master, you have to do merge update code then you will move by putting $ git checkout master so, it will have to give switch.

Now, one command is happen like $ git merge update code then you will have to go in the vs code that file has merged there. When you will have to give a close file from vs code then it will give to see you all files and features that have been added. That files were in an update code, you will see they have been shifted to master, whenever you will put git status then it will see on branch master, working tree clean. When you open vs code by putting $ code. Then you will see comment file will have arrived in the master branch. So, this real meaning happens of merge, it is a very good feature. Suppose, you are making a code differently or doing the work of some other person and after that, you have to do merge all of the codes then only you will put git merge along with branch name and from which branch. It’s happened only, git shows us all work from professionally or the good way how ideally you are making and doing file. Suppose, you have to make a file of a node in that all Html files would work as backhand, you have to do server-side logics and make something in backhand. So, for giving him the layout, you will make a file of nodes. First, separately, you will have to make a branch then you will write $ git branch, and again, you will put $ git branch node integration, your branch will make. You will again put git branch then the branching file will show now, you have to make a file, and the direct switch also. It means that you make a branch, you want to do a switch. So, one command that is happening is $ git –b nodeintegration.

Adding JavaScript branch

If you will put $ git –b nodeintegration then it will show checkout changes. When you will do $ git checkout node integration then it will be switched to branch node integration. You will make a file in the name $ touch node.js so, you will see a file has been made in a vs code. Suppose, you have written anything in that like

console.log (“this is the server-side language”)  

console.log (“this is git hub training”)

You have done a server-side in the node integration branch. Now, what can you do? Normally, you can check that. Suppose, you do $ git checkout master then your file node configuration will vanish from the vs code. You have made a file then first, you will add by putting $ git add –A so, it will come in the staging area. Next, you will do it by putting $ git commit –m “this is server-side js file” then the file will be added so, you have committed all files. Suppose, you have to give branch change by adding $ git checkout master when you do switch from the master then the node.js file will have vanished because your file doesn’t exist in the master branch, it will exist in the node integration. Again, you will put as $ git checkout nodeintegration so, the file will be retrieved again in the vs code. It is the meaning of branch, and merge. You have looked at it.

Related video:

Hello techies, welcome to the configurable world of programming. Today, we are going to talk about facts that matter obviously in your git command order. Whether you have fear regarding the command line. After reading, these awesome steps, you will be gain more awaking and stability on the command line. Perhaps, before learning new stuff or things, you have doubt on either you will be eligible or not in getting that. So, this comprehensive part will make you precisely expert in the daily upcoming command matters.

Four stages of files

Some have terms related to git. Let’s have a look at the terms. There are four stages such as untracked, unmodified, modified, and staged. Let’s look at these four. Whenever we make a repository, initialize the git. There is an untracked file, what does it mean? Just until git is not giving care to them. They will not track them, nothing will do, whatever you will do, it will show untracked to you. If you will do adding the file then it reaches the staging area, what is the staging area? the Staging area is the place where your file is ready to be committed. What is a commit? It means, one type of you have been done all codes, you are ready to upload them. Suppose, you make a program doing little-little now, the program doesn’t make at once. So, Doing little, you are ready to upload, one work, one module has been made, you will upload this, the second module has been made, you will upload that. So that, your file is not going to vanish or lose. This has been happened about staged and untracked. What is unmodified happen? Whenever you do commit, suppose, you have done commit then it will move into the unmodified. After doing the commit, firstly, you will do untracked to add file then it will come in the staged area. Again, what will you do? You will do commit so, it comes in unmodified. Suppose, you have a program, there is a file which is in commit then after, you have added some more commands in that. What will happen next? The file will be modified. Again, you edit that file then it will show you modified because you have modified and added codes to them. Again, you have to do stage the file and commit, you can also remove that file from commit. These all are special stages of commands, you may also see that through the command line. Everything will come in understanding if you will see through the command line. Now, you will move to your git bash and make some files over there. You would make a file from touch, touch is a command which is used for making empty files. Suppose, you want to make a blog site then you need some files like $ touch about.html again, you type $ touch news.html, you have made two files then you will see vs code, the two files will be there to the name of about.html, and news.html. These two files will be empty, you have made these files through the command line. Now, you will check by writing some Html codes so, you can make your own basic structure like Html: 5 then your full page layout will be ready like this,

For about.html,

                        <! DOCTYPE html>

                        <html Lang=”en”>

                        <Head>

                                    <Meta charset=”UTF-8”>

                                    <Meta name=”viewport” content=” width=device-width, initial- scale=1.0”>

<Title> about page</title>

</head>

<Body>

            This is about page

</body>

</html>

For news.html,

                        <! DOCTYPE html>

                        <html Lang=”en”>

                        <Head>

                                    <Meta charset=”UTF-8”>

                                    <Meta name=”viewport” content=” width=device-width, initial- scale=1.0”>

<Title> News page</title>

</head>

<Body>

            This is news page

</body>

</html>

Suppose, you have been made these two things so, again, you put $ git status then there will show untracked files. If you want to track all files then there has a command like $ git add about.html then it will do track. Now, you will put $ git status so, it will show you two files one will be tracked or another will be untracked. Suppose, you have ten to twelve files, very huge projects, and so many files so, you will not do it one by one. For doing at once, what will be the command? Then the command will be $ git add –A so, your all folder files will be shifted into the staging area. When you will type $ git status then all your files will be shown in the staging area. You can do unstage so, you will see just how we can do unstage.

Git commit command

So, lets us do commit this, what would be the command for doing commit? For commit, you will put like $ git commit –m “the first commit” when you do enter from there will be committed with the message. So, there all files will be commit

                        [master (root-commit) 3b17be6] The first commit

                         — Files changed, —- insertions (+)

                        Create mode 100644 .vscode/settings. json

                        Create mode 100644 about.html

                        Create mode 100644 news.html

Get checkout command

Suppose, something has happened as your file has been deleted. At once, you have been done commit after that, your all files are deleted by anyhow or somebody has saved that and closed it. Also, the editor has been closed. So, for retrieving that file, one command is happen there. Through that file, it matches your previous commit so, what are they happen? $ git checkout about.html, you will see that your about.html file will retrieve once again. It means your all files have been deleted after doing save. You have ten to twelve files that have been deleted but one time commit should happen, you have done commit and all your files have been deleted. So, you have to retrieve all files then you will type like $ code. Then your vs code will open. You have saved your file and deleted them, if you have to match these files to the previous commit, those have been deleted and you want to retrieve that files into about.html and news.html. So, the checkout one more command happens like $ git checkout –f, when you will put this then it has been matched all files from the previous commit. You will see that all files are available in vs code, it is a useful command. From here, the benefits will be ready to see you, why do GIT use? For what GIT is used? These all benefits, you will have to see that if your file will have been deleted then how you can retrieve them and match to the previous commit. About these all thing, you are seeing.

Git log command

One more command happens whose name is GIT log. What does it do? When you run the $ git log command then it will show you all details about the first commit like the author, and date. Suppose, you have done a hundred commits so, you will do GIT log then all commits will be retrieved there. If you have to see two or three commits then what will you do there, you will put like $ git log -p -1 so, it shows your last commit in detail with diff. what is diff.? You will see just now, there will show you first commit and what changes you have added in that. When you will press Q then it will happen quit and will move in the editor. Suppose, you make a file like $ git touch contact.html then the file has been done. You will see that your file will be ready in vs code to the name contact.html so, you will write code, as usual, you have written previously in that. You will see a U signal besides contact.html which means it is unstaged and untracked. You would continuously run the $ git status command so that you should know what is happening in your file then it will show you the contact.html file and untracked also. First, you will add that by typing command $ git add –A so, it will come in the staging area. When you will put $ git status then your new file will show there. So, you do any advancement in the news.html file and you have added them in that file then what will show to you?  When you put $ git status then it will show you modified because you have done changes in that.

Again, you have to send in the staging area so, as you will write $ git add –A then it will move to the staging area. So, GIT will hold your all records like what are you doing or not? You will add some features in all files so, again, you will run the command like $ git status then all your files will show you modified. After that, you will do add in staging area and commit that by $ git add –A. Again, you will run $ git status then it will show your all files status, if you will write $ git commit –m “Adding the new features to files” then it will show your file details. Suppose, you have added some features in all files through going vs code, let them will save otherwise, the effect will not happen then again, you will put $ git status so, all will be modified, you want to do a direct commit, without sending them staging area. So, there will be commands like $ git commit –a –m “skipping the staged area” from there, staging area will have to give skip and directly, they will be print so, you can check through $ git log p 2 then everything will show you there. If you will put Q then it will do quit from the editor. When you will do $ ls then it will show you all files, like $ pwd, $ ls command, these all happen unique command, you are using in git then it is also work as a terminal command in git bash. Suppose, you make a file by default to the name $ touch delete.html, you have added some feature in that file then you will type $ git status then it will show you untracked because you have not added in the staging area.

Related video:

1. Installed Xampp

2. Another thing which is required is Composer

3. Now the thing is when we try to install Laravel project inside our htdocs folder it through an error

4. To resolve this error first create a folder inside your htdocs.

mkdir Projects

5 grant read and write permissions to this folder by running this commands

sude chmod +rw Projects

6. You may get another error while installing is (“mbstring” extension is missing.)

Run the below commands to resolve these errors

sudo apt-get install php-mbstring

sudo su - root

7. That’s it now try installing your project again

composer create-project --prefer-dist laravel/laravel testProject "5.8.*"

That’s it, Hope it help someone out there.

Note: The steps below will permanently delete all Docker containers, images, volumes, and networks stored on your machine. Back up anything you need before proceeding.

Step 1: Stop the Docker Service

Before removing any packages, stop the Docker daemon to avoid file-in-use errors:

sudo systemctl stop docker
sudo systemctl disable docker

Step 2: Remove Docker Packages

Use apt-get purge to remove the Docker packages along with their configuration files, then autoremove to clean up any unused dependencies:

sudo apt-get purge docker-engine docker docker.io docker-ce docker-ce-cli containerd.io
sudo apt-get autoremove --purge docker-engine docker docker.io docker-ce containerd.io
sudo apt-get autoclean

The exact package names vary depending on how Docker was installed (from the Ubuntu default repositories versus the official Docker repository). Running the command with all common package names is safe — apt-get will simply skip packages that are not installed.

Step 3: Remove Docker Data Directories

apt-get purge does not remove Docker’s runtime data: images, containers, volumes, and custom networks are stored separately in /var/lib/docker. Remove them manually:

sudo rm -rf /var/lib/docker
sudo rm -rf /var/lib/containerd

Step 4: Remove Residual Configuration and Binary Files

Docker may leave behind configuration files, CLI plugins, and systemd unit files in several locations. Remove them with the following commands:

# Docker configuration directory
sudo rm -rf /etc/docker

# systemd drop-in and service files
sudo rm -rf /etc/systemd/system/docker.service.d
sudo rm -f /etc/systemd/system/docker.service
sudo rm -f /etc/systemd/system/docker.socket

# Docker context and CLI config (per-user)
rm -rf ~/.docker

# Reload systemd after removing unit files
sudo systemctl daemon-reload

Step 5: Remove the Docker APT Repository and GPG Key

If you added Docker’s official APT repository, remove it so it does not interfere with future package operations:

# Remove the repository source file
sudo rm -f /etc/apt/sources.list.d/docker.list

# Remove the GPG keyring (path may differ based on how it was added)
sudo rm -f /usr/share/keyrings/docker-archive-keyring.gpg
sudo rm -f /etc/apt/keyrings/docker.gpg

# Update the package index
sudo apt-get update

Step 6: Remove Docker Groups and Users

Docker installation creates a docker system group. Remove it if it is no longer needed:

sudo groupdel docker

If the command returns a “group does not exist” error, the group was already removed by the package purge step — that is fine.

Step 7: Verify No Docker Files Remain

Run a filesystem search to confirm that Docker-related files are gone. Be aware that some paths — such as entries under /proc, /sys, and /run — are virtual/pseudo-filesystems and will not persist after a reboot. Entries there do not necessarily indicate a problem:

sudo find / -name '*docker*' 2>/dev/null

After completing the steps above, any remaining results should be limited to virtual kernel filesystems (/proc, /sys) or user-level cache entries. A reboot will clear ephemeral entries in /run and /proc.

Understanding Residual Paths

When the original community question (sourced from askubuntu.com) ran the find command after purging Docker, it discovered references in the following top-level directories:

• /etc — Persistent configuration files not removed by purge
• /lib or /usr/lib — Shared libraries or systemd unit files
• /usr — Binaries, man pages, and CLI plugins
• /var — Runtime data: images, containers, volumes
• /run — Ephemeral runtime sockets and PID files (disappear after reboot)
• /sys — Virtual kernel filesystem entries (disappear after reboot)
• /proc — Virtual process filesystem entries (disappear after reboot)

The steps in this guide address the persistent paths. Entries under /run, /sys, and /proc are managed by the kernel and will be absent after the next reboot.

Quick Reference: Full Removal Script

The commands below combine everything into a single sequence you can run on an Ubuntu/Debian system. Review each line before executing.

#!/usr/bin/env bash
set -e

# 1. Stop and disable the Docker daemon
sudo systemctl stop docker 2>/dev/null || true
sudo systemctl disable docker 2>/dev/null || true

# 2. Purge Docker packages
sudo apt-get purge -y \
  docker-engine docker docker.io \
  docker-ce docker-ce-cli docker-ce-rootless-extras \
  containerd.io
sudo apt-get autoremove --purge -y
sudo apt-get autoclean

# 3. Remove data directories
sudo rm -rf /var/lib/docker /var/lib/containerd

# 4. Remove configuration and service files
sudo rm -rf /etc/docker
sudo rm -f /etc/systemd/system/docker.service \
           /etc/systemd/system/docker.socket
sudo rm -rf /etc/systemd/system/docker.service.d
rm -rf ~/.docker

# 5. Remove APT repository and key
sudo rm -f /etc/apt/sources.list.d/docker.list
sudo rm -f /usr/share/keyrings/docker-archive-keyring.gpg
sudo rm -f /etc/apt/keyrings/docker.gpg
sudo apt-get update

# 6. Remove the docker group
sudo groupdel docker 2>/dev/null || true

# 7. Reload systemd
sudo systemctl daemon-reload

echo "Docker removal complete. Reboot to clear any remaining ephemeral entries."

After rebooting, re-run sudo find / -name '*docker*' 2>/dev/null to confirm a clean state.