Unixcloudtrainings

05/01/2022

BONNE FÊTE DE TRAVAIL À MES ABONNÉS.

NOUVEL ARRIVAGE LAPTOPS DISPONIBLE.

07/21/2021

Learn DEVOPS in the cloud hands on.

07/21/2021

07/21/2021

DEPLOYING A JAVA BASED APPLICATION TO AWS CLOUD ☁️

07/19/2021

Once upon the time, a combination of this simple command, options and arguments helped me solve an issue in my case I was facing while working on a project.
Basically, We wanted to create a folder 📂 to have people to work inside together in a collaborative manner without having to add any single user to the group of the other user to gain access to a file content. I think you’ve already guessed the type of O.S(Linux) I was working on: RHEL7. Many people might know this technique and some not. The whole idea 💡 was to create a common group for those user’s accounts and add them inside giving them READ WRITE and EXECUTE permission according to what we wanted them to perform. But if you’ve noticed well we did solved the problem yet because remember we needed to have them accessing each other folder/files without herculean efforts. So, the solution was to do this:
Assign the group ownership to the common group, add all the users to the common group and use this command “chmod g+s common_folder_name”.

As simple it is, this is called Setgid in the Linux system administration world because it will cause any file/directory created under a common folder to belong to a specific group avoiding us to add 1000s of users into a single group each time to have access to a specific file/directory content under that folder.

Now how do you give a permission to a specific user on a file/folder without assigning him/her to a specific group using ACL(Access Control List)?

What was your recent challenge at work?

07/19/2021

07/17/2021

Wanna learn Linux, windows server, kubernetes & aws cloud at once kindly contact us

07/16/2021

We recently announced that We will produce a GitHub repository to document the way We implemented my Jenkins Master to build its jobs remotely over a Jenkins slave on a Docker platform. The project is not perfect and you might find a better way to do it. Please fork it if you want to and initialize any pull requests so I we can I learn from my mistakes.
Here is the link get it: https://github.com/ngostal2019/jenkins_master_slave_docker

07/16/2021

A couple of weeks ago, we decided to work on a project where we had to connect a Jenkins master with a slave agent over the Docker platform so that all the builds would be executed remotely on the Docker slave agent which wasn’t easy at all. You have to make a lot of researches and also fail couple of times to achieve that. We almost gave up to this project until today we decided to give it a go and the final result is just astonishing. We are now planning to make a GitHub repository (ngostal2019/Jenkins_master_slave) of it if you want to try it on your own avoid you to hassle like us to realize this project.

Follow us to get updates when we will publish the final repository on GitHub

Lesson learn is that never give up because you might be already close to your target 🎯 at the time you’re giving up.

07/05/2021

New session will start in September.