SERGEY DOVBENKO’s Post

Day 3 of My DevOps Journey Today was all about getting hands-on with Linux fundamentals — an essential building block for any DevOps engineer. I explored key commands and concepts such as: 🔹 User & Group Management: "adduser", "addgroup" 🔹 File Ownership: "chown" 🔹 File Permissions: "chmod" 🔹 File Management & understanding permission structures It’s fascinating to see how much control Linux gives over users, access, and security. These concepts might seem basic, but they form the backbone of managing real-world systems effectively. Every day is a step closer to becoming proficient in DevOps Looking forward to diving deeper tomorrow! #DevOps #Linux #LearningInPublic #CloudComputing #SystemAdministration #TrainwithShubhum

Day 07 of #90DaysOfDevOps 🚀 Linux File System Hierarchy: Know Where Everything Lives Today I stopped treating Linux as a black box. Time to think like an operator. Every DevOps engineer should know where to look first: → `/etc` — configuration files (nginx, ssh, hosts) → `/var/log` — first stop during incidents → `/tmp` — temporary files → `/opt` — third-party tools (Jenkins, Grafana) → `/home` / `/root` — user environments and permissions What I practiced today: ✅ Mapped core Linux directories with real-world use cases ✅ Diagnosed a failed service using `systemctl status` + `journalctl` ✅ Identified CPU-heavy processes with `ps aux --sort=-%cpu` ✅ Resolved permission issues using `chmod +x` ✅ Located service logs with `journalctl -u <service>` 💡 Most useful takeaway: A service failing after reboot isn't always a crash issue — sometimes it was never enabled to start. Verified with `systemctl is-enabled`. 🔑 Mindset Shift: In production, speed comes from knowing where to check, what to run, and what signal matters first. #90DaysOfDevOps #DevOpsKaJosh #TrainWithShubham #Linux #DevOps

DevOps Zero to Job-Ready – Day 8/180 | Process Management Process management is a core part of working in Linux systems. What this covers: * Running background processes: `sleep 300 &` * Finding processes: `ps aux | grep sleep` * Stopping processes: `kill <PID>` * Force stopping: `kill -9 <PID>` Key point: `kill` stops a process gracefully, `kill -9` force terminates it. Force kill should only be used when necessary. Sharing today’s notes. More structured DevOps content available on [www.engidock.com](https://www.engidock.com). Next: Monitoring processes using top & htop #DevOps #Linux #LearningInPublic

DevOps Zero to Job-Ready – Day 8/180 | Process Management Process management is a core part of working in Linux systems. What this covers: * Running background processes: `sleep 300 &` * Finding processes: `ps aux | grep sleep` * Stopping processes: `kill <PID>` * Force stopping: `kill -9 <PID>` Key point: `kill` stops a process gracefully, `kill -9` force terminates it. Force kill should only be used when necessary. Sharing today’s notes. More structured DevOps content available on [www.engidock.com](https://www.engidock.com). Next: Monitoring processes using top & htop #DevOps #Linux #LearningInPublic

🔍 Mastering the sed Command in Linux 🐧 The sed (Stream Editor) command is one of the most powerful tools in Linux for text processing and automation. Whether you're a DevOps engineer, developer, or system administrator, sed can significantly simplify your daily tasks. 🚀 Here are some practical use cases: ✅ Updating environment variables for different environments (dev → prod) ✅ Modifying Docker image versions in deployment files ✅ Editing Kubernetes YAML configurations dynamically ✅ Replacing IP addresses or domain names in config files ✅ Cleaning and filtering log files efficiently ✅ Performing bulk updates across multiple files ✅ Commenting and uncommenting configuration lines ✅ Inserting new configuration values automatically ✅ Dynamically updating secrets in CI/CD pipelines ✅ Replacing URLs in application code #Linux #DevOps #CloudComputing #Automation #Scripting #Docker #Kubernetes #CI_CD #AWS #TechSkills

Linux Troubleshooting - Real Production Scenarios. 2 AM. Pager goes off. “Server is down.” No documentation. No hints. Just you, a terminal, and production pressure. Here are real troubleshooting scenarios every DevOps engineer should know #Linux #DevOps #SRE #Troubleshooting #SysAdmin #CloudEngineering #100DaysOfDevOps #InfrastructureAsCode #LinuxAdmin #TechCommunity

Mastering the Command Line = Mastering Linux 💻🐧 One step closer to becoming a DevOps engineer — I just deep-dived into Linux file management from the command line! Here's what I'm getting comfortable with: 📁 Navigating the Linux file system hierarchy 🔍 Commands like ls, cp, mv, rm, mkdir, and find 🎯 Shell wildcards & path expansion 🗂️ Understanding /home, /etc, /var, /usr — where everything lives The terminal used to look scary. Now it's where I feel most powerful. No GUI. No mouse. Just pure command-line efficiency. Every command I master today is building the foundation for my DevOps career tomorrow. On to the next skill! 🚀 #Linux #RedHat #DevOps #CommandLine #SysAdmin #TechSkills #LearningJourney #CareerGrowth #OpenSource

Mastering Linux User Management is a must-have skill for every DevOps Engineer 💻⚙️ From creating users to managing permissions and groups, these commands form the backbone of secure and efficient system administration. Whether you're preparing for interviews or working in real-world environments, having these commands at your fingertips can save time and boost productivity 🚀 👉 Keep learning. Keep building. Keep automating. #Linux #DevOps #SystemAdministration #CloudComputing #Automation #DevOpsEngineer #LinuxCommands #TechSkills

This week in my DevOps journey, I focused on Linux fundamentals. I covered the basics of how the Linux system is structured, including the root directory and how files and folders are organised. I also got hands-on with essential commands for navigating the system, creating and managing files, and searching through data using tools like grep and find. One key takeaway for me was understanding the importance of log files. Instead of guessing when something goes wrong, logs help you see exactly what happened and where things failed. I also started learning how DevOps engineers approach debugging, checking services, reading logs, identifying the root cause, and verifying fixes. Still early in the journey, but starting to see how these fundamentals connect to real-world systems. #DevOps #Linux #LearningInPublic #TechJourney