🚨 The first time I opened a Linux server… I saw folders like `/bin`, `/etc`, `/var`, `/home` and thought: “What is all this? And why is everything starting with `/`?” 😅 That confusion led me to learn something very important for DevOps. 💡 𝘋𝘢𝘺 9 𝘰𝘧 𝘮𝘺 𝘋𝘦𝘷𝘖𝘱𝘴 𝘑𝘰𝘶𝘳𝘯𝘦𝘺 Today I learned about the 𝗟𝗶𝗻𝘂𝘅 𝗙𝗶𝗹𝗲 𝗦𝘆𝘀𝘁𝗲𝗺 — the structure that organizes everything inside a Linux system. --- 📖 Think of it like a 𝗺𝗮𝗽 𝗼𝗳 𝘁𝗵𝗲 𝗲𝗻𝘁𝗶𝗿𝗲 𝗼𝗽𝗲𝗿𝗮𝘁𝗶𝗻𝗴 𝘀𝘆𝘀𝘁𝗲𝗺. In Linux, everything starts from a single root directory: 👉 `/` (root) From there, the system branches into different directories, each with a specific purpose. --- Here are some important ones I learned today: 📁 /𝗯𝗶𝗻 Contains essential command binaries like `ls`, `cp`, `mv`. 📁 /𝗲𝘁𝗰 Stores system configuration files. 📁 /𝗵𝗼𝗺𝗲 Personal directories for users. 📁 /𝘃𝗮𝗿 Contains logs, cache, and variable data. 📁 /𝘂𝘀𝗿 Stores system programs and utilities. 📁 /𝘁𝗺𝗽 Temporary files used by applications. --- 🚀 𝘞𝘩𝘺 𝘵𝘩𝘪𝘴 𝘮𝘢𝘵𝘵𝘦𝘳𝘴 𝘪𝘯 𝘋𝘦𝘷𝘖𝘱𝘴? Because when you manage servers, deploy applications, or troubleshoot issues… You constantly interact with these directories. Knowing 𝘄𝗵𝗲𝗿𝗲 𝘁𝗵𝗶𝗻𝗴𝘀 𝗹𝗶𝘃𝗲 𝗶𝗻 𝗟𝗶𝗻𝘂𝘅 saves a lot of time when debugging systems. --- 🔥 𝘔𝘺 𝘣𝘪𝘨𝘨𝘦𝘴𝘵 𝘳𝘦𝘢𝘭𝘪𝘻𝘢𝘵𝘪𝘰𝘯 𝘵𝘰𝘥𝘢𝘺: Linux is not random. Every directory has a 𝘀𝗽𝗲𝗰𝗶𝗳𝗶𝗰 𝗿𝗼𝗹𝗲 𝗶𝗻 𝗸𝗲𝗲𝗽𝗶𝗻𝗴 𝘁𝗵𝗲 𝘀𝘆𝘀𝘁𝗲𝗺 𝗼𝗿𝗴𝗮𝗻𝗶𝘇𝗲𝗱 𝗮𝗻𝗱 𝘀𝘁𝗮𝗯𝗹𝗲. --- 📌 𝘚𝘮𝘢𝘭𝘭 𝘬𝘯𝘰𝘸𝘭𝘦𝘥𝘨𝘦 𝘭𝘪𝘬𝘦 𝘵𝘩𝘪𝘴 𝘣𝘦𝘤𝘰𝘮𝘦𝘴 𝘱𝘰𝘸𝘦𝘳𝘧𝘶𝘭 𝘸𝘩𝘦𝘯 𝘸𝘰𝘳𝘬𝘪𝘯𝘨 𝘸𝘪𝘵𝘩 𝘴𝘦𝘳𝘷𝘦𝘳𝘴 𝘢𝘯𝘥 𝘤𝘭𝘰𝘶𝘥 𝘪𝘯𝘧𝘳𝘢𝘴𝘵𝘳𝘶𝘤𝘵𝘶𝘳𝘦. And that’s exactly what DevOps engineers deal with daily. --- 💬 𝘋𝘦𝘷𝘖𝘱𝘴 𝘦𝘯𝘨𝘪𝘯𝘦𝘦𝘳𝘴 𝘩𝘦𝘳𝘦 — Which Linux directory confused you the most when you started? 😅 --- Learning step by step 🚀 #DevOps #Linux #LinuxFileSystem #LearningInPublic #DevOpsInsiders #TechJourney

Day 5/100: Setting up the Command Line Lab 🖥️ Today was all about the terminal. No "Next-Next-Finish" installers—just pure Linux package management to set up my DevOps workstation. I spent the day configuring my local environment on a RedHat-based system using dnf and yum. Setting up these tools via the CLI is the best way to understand how we'll eventually manage thousands of servers in the cloud. What’s now ready in my lab: 🏗️ Virtualization: VirtualBox 7.1 & Vagrant (ready to spin up test VMs). ☕ Java Stack: OpenJDK 17 & Maven (for building enterprise-grade apps). 🌿 Version Control: Git (installed and ready for the first commit). 📝 Editor: VS Code (configured via the official Microsoft repo). The 'Aha!' Moment: Realizing that every tool we use—from Vagrant to VS Code—can be installed and updated using simple commands. This is the first step toward Infrastructure as Code (IaC). With the lab officially built, I'm ready to dive into the core of every DevOps engineer's life: Some Sign-up #100DaysOfDevOps #100DaysOfDevOpsChallenge #DevOps #Linux #Vagrant #VirtualBox #Automation #LearningInPublic #CloudEngineer

Ever wondered what actually powers your containers when you strip away the Docker magic? 🪄 ➡️ ⚙️ We know containerd runs in the background of almost every modern Kubernetes node, but installing it manually from scratch is the best way to reveal exactly how the engine ticks. I just published part three of my deep-dive series: "How to Install and Configure containerd on a Linux Server." We are dropping the training wheels. No pre-packaged Docker engines. We are pulling the raw binaries and wiring up the decoupled stack entirely by hand. In this hands-on guide, you will learn how to: ✅ Extract and install the core components (ctr, daemon, and OCI shim). ✅ Daemonize the container engine using systemd. ✅ Plug in a low-level OCI container runtime (runc). ✅ Install and configure CNI plugins (bridge, loopback) to establish container networking. If you are a Platform Engineer, SRE, or DevOps professional wanting a crystal-clear mental model of your container architecture, this one is for you. Check out the full guide here on Systems and Signals: 👉 https://lnkd.in/dZ-z_SeP #Containerd #Kubernetes #Linux #CloudOps #SRE #DevOps #PlatformEngineering #SystemsAndSignals #TechTutorial

Phase 4 done. My app is live on AWS. And it was not easy. 😅 I thought deployment would be the simple part. Write some Ansible tasks, run the playbook, done. Nope. Here is what actually happened: ❌ PM2 kept crashing — Ansible ran it as root, blocking port 5000 ❌ Git refused to clone — the folder was owned by root, not ubuntu ❌ MongoDB refused connections — it only listened on localhost by default ❌ React showed 404 — Express had no instruction to serve static files ❌ Wrong build path — server.js was looking in the wrong folder Every single issue had a different root cause. Each one taught me something real about Linux, permissions, and how apps run in production. After fixing all of it: ✅ Both web servers running on port 5000 ✅ React built with the ALB URL baked in ✅ MongoDB connected and storing data ✅ PM2 running as ubuntu user, not root ✅ Load Balancer showing both targets healthy 👉 Watch the video to see the app running live via the ALB URL. This is Phase 4 of my DevOps project: deploying a MERN app on AWS using Terraform + Ansible. #DevOps #Ansible #AWS #MERN #LearningInPublic #CloudComputing #Docker #Linux #Terraform

🚀 Deploying LAMP Stack using Podman Pods! Excited to share my recent hands-on experience with containerization and Podman 🚀 🔧 Objective: Successfully deployed a LAMP (Linux, Apache, MySQL, PHP) stack using the Pod concept in Podman. 💡 What I Learned: Creating and managing Pods in Podman Running multiple containers (Apache, MySQL, PHP) in a single Pod Enabling seamless communication between containers Understanding real-world container orchestration basics 📌 This task helped me strengthen my practical knowledge of containerized environments and how services work together in a unified setup. 💻 Exploring more in DevOps, Cloud & Automation! #Podman #LAMPStack #DevOps #Linux #Containerization #CloudComputing #RHCSA #LearningByDoing #Automation

🚀 Day 6 of My DevOps Journey | Linux Administration & Web Server Setup Today I explored deeper into Linux system administration, covering file ownership, networking, package management, and web server setup. 👤 Ownership & Permissions Used chmod to manage file permissions Used chown to change file ownership Learned difference: chmod → controls access chown → controls ownership 🔍 File Search & Management Used find command to locate files Found empty files & directories Deleted old files using time-based filters 📦 Package Management Installed software using yum (Amazon Linux / RHEL) Verified installations (git, java) Checked paths using whereis 🌐 Networking Commands ping → check connectivity wget → download files curl → send HTTP requests ifconfig → check IP address 🗜️ Zip Operations Compressed files using zip Extracted using unzip 🌍 Web Server Setup (Apache - httpd) Installed Apache server Started service using systemctl Hosted a static website using /var/www/html Accessed website via public IP ⚙️ Service Management Used systemctl to: start / stop / restart services manage background processes 📊 System Monitoring top, htop → running processes free → memory usage uptime → system running time 💡 Key Learning: Linux is not just commands — it’s about managing systems, users, services, and real-world infrastructure. #DevOps #Linux #AWS #CloudComputing #SystemAdmin #WebServer #LearningJourney

Every DevOps engineer I know has a version of this saved somewhere. If you're working with AWS, Docker, Kubernetes, or any CI/CD pipeline, you're working with Linux. No way around it. Shubham Praharaj put together a clean 29-page cheat sheet covering 20 core Linux topics. Saved it, went through it, and honestly, it's one of the better ones I've seen floating around. What's covered: → Directory structure & basic commands → Vim editor (modes, shortcuts, DevOps use cases) → File permissions & chmod/chown → User management & sudo access → Process & package management → Service management with systemd → Network config & firewall (UFW, firewalld, iptables) → Troubleshooting & log analysis Whether you're prepping for interviews or just need a quick reference on your server, grab the link from the first comment. #Linux #DevOps #CloudComputing #SysAdmin #CheatSheet #AWS #Docker #Kubernetes #CICD #LinuxAdmin #ITTraining #SMEnodeAcademy #DevOpsTools #InfrastructureAsCode #ShellScripting

DevOps can look very polished from the outside. • Cloud dashboards • Automated pipelines • Clean web interfaces • Seamless deployments Everything feels fast, modern, and under control 🚀 Until production breaks. And then… everything shifts back to fundamentals: • SSH into servers • Dig through /var/log • Run Linux commands to trace issues • Write quick Bash scripts to patch things up That’s when the reality becomes clear— No matter how advanced the stack is, it still runs on: • Linux • Bash • CLI tools These aren’t flashy. They don’t have dashboards. But they are the backbone of everything we build. At the end of the day, when systems fail, it’s not the UI that saves you — it’s your fundamentals. Takeaway: You can ignore Linux and Bash early on, but in real-world DevOps… the terminal is inevitable. #DevOps #Linux #Bash #CloudComputing #AWS #Automation #CloudEngineer #TechJourney

🐧 Stop Googling, Start Typing: The Ultimate Linux Cheat Sheet! 🚀 Ever feel like the Linux terminal is a secret club you don’t have the password for? It’s time to change that. 💻 Whether you’re a Developer, SysAdmin, Student or DevOps Engineer, mastering the command line isn't just a flex—it’s a massive productivity multiplier. To help you navigate the shell like a pro, I’ve compiled the "Essentials" into one easy-to-save guide. 📌 What’s Inside the Toolkit: 📂 File & Directory Management: Navigate, create, and organize with ease (ls, cd, mkdir, rm). 👤 User & Permissions: Take control of security (chmod, chown, sudo). ⚙️ Process Handling: Monitor and manage system resources like a boss (top, ps, kill). 🌐 Networking Basics: Troubleshoot and connect instantly (ip addr, ping, netstat). Mastering Linux isn't about memorizing 1,000 commands—it’s about knowing the right 20 that get 80% of the work done. 🌟 _______________________________________________________________ 📥 [DOWNLOAD/SAVE THIS POST] 📥 Don't let this get lost in your feed. Hit the Save button and keep this reference handy for your next terminal session! Which Linux command saved your life today? Let's talk in the comments! 👇 #Linux #CheatSheet #SysAdmin #DevOps #Programming #TechSkills #OpenSource #DeveloperJourney #LinuxCommands #Networking #DevopsEngineer #AWS #Linuxpdf

🔐 Day 4 of #100DaysOfDevOps — Linux file permissions Today's task: a backup script existed on a production server but no one could run it. One missing permission bit was the culprit. Here's what I learned: Every Linux file has a 10-character permission string like -rw-r--r-- It's split into 3 groups: → Owner (the user who created it) → Group (a team sharing access) → Others (everyone else) Each group gets 3 bits: r (read=4), w (write=2), x (execute=1) The fix was one command: chmod a+x /tmp/xfusioncorp.sh or chmod 755 /tmp/xfusioncorp.sh a = all users | +x = add execute permission Before: -rw-r--r-- (no one can run it) After: -rwxr-xr-x (everyone can run it) Why does this matter in DevOps? → Automation scripts fail silently when permissions are wrong → CI/CD pipelines break if deploy scripts aren't executable → Every cloud server you ever manage will need this The numeric equivalent: chmod 755 Meaning: owner gets rwx (7), group gets r-x (5), others get r-x (5) "r = read, w = write, x = execute. Three bits. Three groups. That's all of Linux permissions." #DevOps #Linux #BashScripting #chmod #CloudEngineering KodeKloud