Hello everyone, welcome to the wonderful part of the programming session on that where we had left the most important sections of GitLab CI/CD. Now, we are going to start from where we had left on the accounts of the creation of the .gitlab-ci.yml file or how to run the CI/CD pipeline. If you want to learn from scratch so, you may visit previously happened articles for proper assistance. So, let’s start with the rest part of the topic that describes most parts of the GitLab CI/CD.

Create .gitlab-ci.yml file

Step 1: Add .gitlab –ci.yml in the root folder of your projects/repo

I’m starting from where I had left the rest part of creating the GitLab YML file. So, after saving your project, you will go to your desktop and you will press command shift and dot on your keyword because this will be your hidden file you will copy that and move it to your projects folders you will have created a project and in the project folder, you had created a folder called GitLab in GitLab you had your first project. The same thing you can do in windows so the steps will remain the same you can just copy it in your projects folder wherever it is so it will be there your first projects you can just copy that file there so, you can actually copy that file there. Now, this was step number one and you will also copy the contents of that file so, you will see it you can also copy that in notes that will be the file you will have created this was step no. one and now, the step no. two is

Step 2: commit and push file to GitLab repository  

So, now because you have added that in your project you just need to commit and push in your gitlab repository you will have already know the commands for committing and pushing so, open your terminal there if you will on windows you can open git bash or the command line and first you will change the location to your project so, you will see say CD and go to your project folder and there if you say git status you will see you are getting that file will not yet added so you will say git add dot and all these comments you have learnt and then you will say git commit so if you again say git status you would see it in green so you will see now it will be added and then now you will say git commit –m “ added .gitlab-ci.yml file  and now you will push say git push –you origin/ master so you have you will give the URL instead of origin so there you will add the URL of your repository you will go to gitlab and go to your project and there you will click on clone and copy this HTTP link and provided there and hit enter if you will not have added your credentials there and you believe you have done it on windows you wil go to your command line and go to the location of your project there and now you will say git status and your file will be having there. You will say git add and git status again you will now say git commit –m “added .gitlab-ci .yml” and you would say git push –u origin master or you will say git push –u and give the link there of your first project they would push the changes if you go and check your project now you would have your GitLab CI ml file there so you will see now it will be there so you had pushed the changes.

Run CI/CD pipeline

 Now, the next thing is step no. three will be

Step 3: Create GitLab runner for the projects

So, if you go to your project you will go to your project go to settings and there you would go to CI/CD and in the runner, if you expand you will see you will have this runner created earlier so this runner will have already created so, this we have already done step no. three. Step no. four will also make sure that the runner that you are using has your tag that you will have given in your ml file so you will have your tag there CI that you will have given in your ml file now step four will be

Step 4: Start the runner  

Now, you will start the runner so, you will also start from your Mac or windows anywhere you will have learned this how to start so you will just say there brew service says start GitLab you don’t know if you will go to GitLab runner so, there is the documentation for GitLab runner so, you are on windows you will see there you will have for Mac for windows all these things you will have. And you can use this so if you are on windows you can just run this GitLab runner .exe start so there that will have already started so that is fine so you can start and stop but that is fine it will be started so once you can start that or now then step no. five will be

Step 5: Make any change in the project >> commit >> push

 So, basically what you will have done is you have added this CI job or you had added this GitLab CI YML file in your project that will now check for any commits and push in the project whenever you do any commits it will if you will have runner running if you will have GitLab runner running having the same tags like what you will have given in the file. For example: you will have given CI there then it will start the job whatever you will have given in the CI file in the gitlab CI file so now you will make some change there you will go there to your project and you will just some file there or you will not add a folder you will just add a file you will say new file you will say that is test 1.txt that will be test file and you will save and close it if you will go to your command line if you will say git status that will be added so you will say git add you can say test1.txt or you can say dot for everything and you will say git commit –m “added test1 .txt” and now you will have to push so you will say git push –u and the URL and master and once you do this when you will go to your projects there and you will go to CI/CD and once you will go there you will see this job’s getting triggered in the job section and you will push that if you will go there and refresh or you will go to the jobs you will see it is now there it will say pending so this is that will run now if you will go inside you will see that is a demo job one that you will have created in your gitlab CI file if you will click there you will see this is running and that will be now passed and you will see it is running hello World so it will say echo hello world and it will be printing hello world and you will see the locks there you will scroll from there that was a very small job so you don’t have lot of logs you can erase the job log you can see the complete raw log all that you can do so now on every commit and push in project it will check if you will have gitlab runner running and you will have this CI file the gitlab CI file it will run the file and whatever jobs you will have added whatever scripts you will have added it will run accordingly so from now on words whenever you will make changes it will triggers that jobs whatever you will have configured in your file so this is in very basic way how you can get started  with gitlab CI/CD of course there are lot of complex yml file set you can create as per your needsif you will go to the gitlab documentation you will see examples and samples of a lot of yml file and you can check them and see how you can use them so, this was the beginning of gitlab CI/CD at a very basic level so, I hope all this will very useful for you please do a hands-on and try some more jobs running some more jobs and gitlab CI/CD.                

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 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:

Step :1 Create a folder anywhere in your local computer with any name (Mine is workspace)

Step:2 Make sure git and gitbash is installed in your local machine if not download it from here

Step:3 Login into your GitHub account and create a repository

Step 4: Clone the repository into your local machine

• get inside your repository

• Copy the URL under HTTPS area
• There are many more ways to clone a repo but for time being use this method
• Now get inside our workspace folder that we created before (local/workspace)
• right click and open git bash or command line inside the folder

• Run these git commands to get started

git init 

This is to initialize a new, empty repository 

git clone https://github.com/pradeeprjth/laravelTestingProject.git [HTTPS_URL_YOU_COPYED_FROM_GITHUB] 

This will clone everything stored in your remote repository into your local folder/repository
You will find a folder with the same name you created your repository 

Step :5 paste your project/code inside the folder you just clone from the repository

• Again run the below commands to push all the changes and codes back to the repository
• Right click and open your git bash or cmd inside the folder

git add .

The git add command adds a file to the Git staging area. This area contains a list of all the files you have recently changed.

git commit -m"first_commit"

git commit creates a commit, which is like a snapshot of your repository. These commits are snapshots of your entire repository at specific times. and you need to specify a commit message using -m flag including double quote

git push origin master    or    git push origin main 

git push -u origin master is used for pushing local content to GitHub

Step 6: Login to your remote machine or ubuntu machine and make sure xampp and composer is installed in that machine.

Follow this blog if xampp and composer are not installed in your remote/ubuntu machine

1. Installed Xampp

How to install and Configure XAMPP on Ubuntu?

This blog is written by Rajesh thanks to him.

2. Another thing which is required is Composer

Install composer using CLI in ubuntu (Globally)

Follow this to install composer in your machine using CLI

Stpe :7 Go to your htdocs folder or if you have lampp then www folder and run below commands

git init 

 This is to initialize a new, empty repository but this time inside your remote machine 

git clone https://github.com/pradeeprjth/laravelTestingProject.git [HTTPS_URL_YOU_COPYED_FROM_GITHUB]

Now as we already have pushed all our code into our repository so we'll get all the files folder into our htdocs folder or www folder 

Step 8: Now to run the project we need to do some configuration

• Copy the .env.example file to .env coz git ignore some files and folder including our vendor folder which contains all our Laravel project files . To do this run the below command.

cp .env.example .env

• Install composer, as git ignores our vendor folder in order to get it back we need to run

composer install

• You may get an error while composer install
• Class ‘Illuminate\Support\facades\Schema not found
• In order to solve this go to your project folder in local and inside C:\xampp\htdocs\WrokSpace\laravelTestproject\app\Providers\AppServiceProvider.php
• use this class in the top
  use Illuminate\Support\Facades\Schema;

• Next thing is to set the APP_KEY value in your .env file, run the command below

php artisan key:generate

Step 9: Now go to your browser and put your ip followed by the project name /public to visit the application

http://90.437.1965.252/laravelTestproject/public/

That’s it hope it help’s someone out there.