<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[CooDev - Medium]]></title>
        <description><![CDATA[DevOps Community - Medium]]></description>
        <link>https://medium.com/coodev?source=rss----560f2d787c4c---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>CooDev - Medium</title>
            <link>https://medium.com/coodev?source=rss----560f2d787c4c---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 21:15:49 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/coodev" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Learning Git for DevOps Engineers/ CooDev]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/coodev/learning-git-for-devops-engineers-coodev-3141f1955c13?source=rss----560f2d787c4c---4"><img src="https://cdn-images-1.medium.com/max/1200/1*iVKYJjTKK4WqvrpPZnkK1w.jpeg" width="1200"></a></p><p class="medium-feed-snippet">Getting Started</p><p class="medium-feed-link"><a href="https://medium.com/coodev/learning-git-for-devops-engineers-coodev-3141f1955c13?source=rss----560f2d787c4c---4">Continue reading on CooDev »</a></p></div>]]></description>
            <link>https://medium.com/coodev/learning-git-for-devops-engineers-coodev-3141f1955c13?source=rss----560f2d787c4c---4</link>
            <guid isPermaLink="false">https://medium.com/p/3141f1955c13</guid>
            <category><![CDATA[git-practices]]></category>
            <category><![CDATA[git]]></category>
            <category><![CDATA[git-for-beginners]]></category>
            <category><![CDATA[git-tutorial]]></category>
            <category><![CDATA[devops-git]]></category>
            <dc:creator><![CDATA[Kanat Akylson]]></dc:creator>
            <pubDate>Wed, 05 Feb 2025 20:43:23 GMT</pubDate>
            <atom:updated>2025-02-05T16:29:47.485Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Mastering Linux for DevOps: From Basic Commands to Production Troubleshooting]]></title>
            <link>https://medium.com/coodev/mastering-linux-for-devops-from-basic-commands-to-production-troubleshooting-d9ae5233b333?source=rss----560f2d787c4c---4</link>
            <guid isPermaLink="false">https://medium.com/p/d9ae5233b333</guid>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[linux-for-beginners]]></category>
            <category><![CDATA[free-course]]></category>
            <category><![CDATA[linux-for-devops]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Batmaaanpls]]></dc:creator>
            <pubDate>Wed, 29 Jan 2025 21:10:10 GMT</pubDate>
            <atom:updated>2025-01-29T21:10:10.140Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Briefly about Linux</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*fVUNcdMo8HPRLs74" /></figure><blockquote>Before we dive in: If you’re new to Linux, you might be picturing some complex, mysterious operating system used only by hardcore programmers. But here’s the thing — you probably interact with Linux every day without realizing it. That Android phone in your pocket is running on Linux. That smart TV in your living room? Probably Linux. Most of the websites you visit? Yep, hosted on Linux servers.</blockquote><p>Linux is just an operating system, like Windows or macOS, but with a key difference: it’s open source. This means anyone can see its code, modify it, and use it for free. It started as a hobby project by Linus Torvalds in 1991 (hence the name Linux), and now it powers everything from tiny IoT devices to massive supercomputers.</p><p>In my work, I mostly deal with Linux distributions like Ubuntu and Red Hat. Think of these as different flavors of Linux — they all share the same core (called the kernel) but come with different tools and interfaces. You can think of Linux as a car. Distributions are like car brands (Toyota, BMW, VW). They all have an engine and four wheels, but their features and user experience differ.</p><p>Hey there! I’m Bakhtiyar, and I’ve been working as a DevOps engineer for the past 4 years. When I first started, I was overwhelmed by Linux — there were so many commands, configurations, and concepts to grasp. Fast forward to today, and I use Linux daily to solve real production issues. This post isn’t your typical Linux tutorial; instead, I’ll share what actually matters in day-to-day DevOps work.</p><h3>Why Linux for DevOps?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*ZGteUBHIQMW1677V.jpg" /></figure><p>Let me be straightforward: you can’t escape Linux in DevOps. Here’s why:</p><p>Most production servers run on Linux. When I started my first DevOps job, I realized that nearly 90% of our cloud infrastructure ran on Linux-based systems. Even Microsoft Azure heavily uses Linux — that should tell you something!</p><p>But here’s what I wish someone had told me earlier: you don’t need to be a Linux guru. You need to understand the fundamentals and know how to troubleshoot when things go wrong (and trust me, they will).</p><p>Coming back to our car analogy, think of Linux like an engine. You don’t need to know every single component, but you should understand the basics of how it works and what to do when there’s smoke coming out of the hood. In my experience, knowing Linux has saved me countless times during production incidents.</p><p>Let me share a real story from last month: Our team got an alert about high memory usage on one of our production servers. Thanks to basic Linux knowledge, I could SSH into the server, use commands like top and ps to identify a memory leak in one of our Node.js services and restart it before it affected our users. Without Linux skills, this would have been a major incident instead of a 15-minute fix.</p><p>Before we dive deeper, I will not dump 100 Linux commands on you and expect you to memorize them. Instead, based on my experience, I’ll focus on what you’ll actually use in your day-to-day work. Ready? Let’s get started with some hands-on practice.</p><h3>Real Production Problems Where Linux Knowledge Saved Me</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/612/0*JKnmTzV_guxvU62j" /></figure><p>Look, you can read about Linux commands all day, but nothing beats real-world examples. Here are three actual incidents I’ve dealt with, don’t worry if you don’t understand some things I mentioned below, as they include other advanced DevOps concepts. I just want you to understand how useful can the Linux be (Details below changed to protect the innocent, of course):</p><h3>The Mysterious Disk Space Vanisher</h3><p>One morning, our monitoring alerted us that a production server was running out of disk space. The application logs looked normal, but the disk was filling up fast. Using <strong>df -h</strong> showed the disk was 95% full, but where was the space going?</p><p>This is where <strong>du -sh *</strong> in the root directory came in handy. Turned out, our application was writing massive files to <strong>/tmp</strong> without cleaning them up. A quick <strong>find /tmp -type f -mtime +7 -delete</strong> cleared old files (files modified more than 7 days ago), and we added proper cleanup to the application. Time to resolution: 20 minutes.</p><h3>The CPU Hog</h3><p>Our Kubernetes cluster was struggling, with one node showing 100% CPU usage. The usual suspects (application logs, metrics) showed nothing obvious. Enter <strong>top</strong> and <strong>htop</strong>. These commands revealed a single process eating up CPU cycles. The cause? A badly configured scraping job that was running way too frequently. Linux tools helped identify the exact process ID and user running it.</p><h3>The Networking Nightmare</h3><p>A developer couldn’t figure out why their service couldn’t connect to the database. “It works on my machine!” (classic). SSH’d into the production server, ran <strong>netstat -tulpn</strong> to check listening ports and <strong>curl</strong> to test connectivity. Turned out the database port wasn’t allowed in the security group. Simple fix, but without Linux networking commands, we’d have been shooting in the dark.</p><p>The point isn’t to memorize these commands — it’s to understand what tools are available and when to use them. I still Google commands all the time. The key is knowing what’s possible.</p><h3>Essential Linux Commands: A Practical Guide</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*VbbKiTvEPRNjatKn.jpg" /></figure><p>Instead of dumping a list of commands, let’s work through a realistic scenario. Imagine this: You’re on-call, and you get an alert at 2 AM (because production issues love the early morning hours). The alert says “High Memory Usage” on a critical service. Here’s how you’d investigate:</p><p>First, connect to the server:</p><pre>ssh username@server-ip</pre><p>Check system resources:</p><pre># Overall memory usage<br>free -h<br># See top memory-consuming processes<br>top<br># or for a prettier view<br>htop # if installed</pre><p>If you spot the problematic process, dig deeper:</p><pre># Check process details<br>ps aux | grep process_name<br># See open files and network connections<br>lsof -p process_id</pre><p>These aren’t just random commands — they form a troubleshooting workflow I use almost daily. Let’s break down other common scenarios and the commands you’ll actually use:</p><p>File System Operations</p><pre># Check disk space<br>df -h<br># Find large files/directories<br>du -sh * | sort -hr<br># Search for files<br>find / -name &quot;filename&quot; 2&gt;/dev/null</pre><p>Log Analysis (Your Best Friend)</p><pre># View logs in real-time<br>tail -f /var/log/application.log<br># Search logs for errors<br>grep -i error /var/log/application.log<br># Last 100 lines of logs<br>tail -100 /var/log/application.log</pre><p>Process Management</p><pre># List processes<br>ps aux<br># Kill a process<br>kill -9 process_id<br># Check running services<br>systemctl status service_name</pre><p>Here’s something most tutorials won’t tell you: I probably use grep, tail, and systemctl 80% of the time. The rest? I look them up when needed. The real skill is knowing what’s possible and what to Google for.</p><h3>Getting Your Hands Dirty: Setting Up a Linux Practice Environment</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*cEey682JD7ij9elL" /></figure><h4>Setting Up AWS Free Tier</h4><p>Look, you could practice Linux commands on your local machine, but let’s do this properly — the way you’ll work in a real job. We’ll set up a free AWS EC2 instance. Don’t worry about AWS details now; I’ll focus on the Linux part here. (Separate blogpost explaining in detail coming up.)</p><p>Quick steps to get started:</p><ol><li>Head to <strong>aws.amazon.com</strong> and create a free account</li><li>Navigate to <strong>EC2</strong> in the console</li><li>Click “Launch Instance”</li><li>Pick Ubuntu Server 22.04 LTS (it’s free-tier eligible)</li><li>Choose <strong>t2.micro</strong> instance type</li><li>Create a new key pair (download it and don’t lose it!)</li><li>Launch the instance</li></ol><blockquote>Important: Always terminate your practice instances after use. While these instances are free, developing good termination habits is crucial. Speaking from experience — I once forgot to terminate some test instances and learned this lesson the hard way.</blockquote><p><em>Pro tip: Set up AWS billing alerts immediately. These notifications will warn you if any instances start incurring unexpected costs, which can save you from unwanted surprises down the road.</em></p><h3>SSH: Your Gateway to the Server</h3><p>SSH is how you’ll connect to pretty much any Linux server in your career. Think of it as a secure tunnel between your computer and the server.</p><p>If you’re on Windows, download <strong>PuTTY</strong> or use <strong>WSL2</strong>. Mac/Linux users, you’re ready to go. Here’s how to connect:</p><pre># First, set the right permissions on your key file<br>chmod 400 your-key.pem<br># Then connect<br>ssh -i your-key.pem ubuntu@your-server-ip</pre><p>Common SSH headaches I’ve faced (so you don’t have to):</p><ul><li><strong>“Permission denied”</strong>: Usually means wrong key or wrong permissions on the key file (<strong>chmod 400 your-key.pem</strong> should help)</li><li><strong>“Connection timed out”</strong>: Check your security group rules — allow TCP port <strong>22</strong></li><li><strong>“Host key verification failed”</strong>: The server’s identity changed. If you’re sure it’s the right server, remove the old key with <strong>ssh-keygen -R server-ip</strong> (I don’t encounter frequently)</li></ul><h3>Practice</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*Bq8guoa4JpJ7jqjd" /></figure><p>Once you’ve successfully connected to your EC2 instance via SSH, practice the commands we covered above to familiarize yourself with them. Take time to understand the output of each command — this will help you better grasp how they work. You can continue using this instance as a learning environment to experiment with new Linux commands and concepts.</p><p>Remember to observe the results carefully — it’s not just about running commands, but understanding what they do and how they interact with the system.</p><h3>Linux Text Editors: VI/VIM</h3><p>Let me be honest — VI can be frustrating at first. But here’s why you should learn it: it’s on EVERY Linux server. When you’re fixing a config file at 3 AM, you won’t always have your favorite editor available.</p><p>Essential VI commands I use daily:</p><pre>i - Enter insert mode (to actually type)<br>Esc - Exit insert mode<br>:w - Save<br>:w! - Force Save (I use this more)<br>:q - Quit<br>:q - Force Quit (I use this more)<br>:wq - Save and quit<br>dd - Delete line<br>/text - Search for &quot;text&quot;</pre><p>Yes, there are other editors like <strong>nano</strong> (easier) or <strong>emacs</strong> (powerful). But VI’s everywhere, so just learn these basics. You can pick up more commands as you need them.</p><p>Here’s a real scenario: You need to edit the nginx config file:</p><pre>sudo vi /etc/nginx/nginx.conf<br># Press i to enter insert mode<br># Make your changes<br># Press Esc<br># Type :wq to save and quit</pre><h3>Bash Scripting: Automation is Your Friend</h3><p>After a few weeks of work, you’ll notice you’re typing the same commands over and over. That’s where bash scripts come in. Here’s a simple but useful script I wrote to check server health:</p><pre>#!/bin/bash<br>echo &quot;=== Server Health Check ===&quot;<br>echo &quot;Memory Usage:&quot;<br>free -h<br>echo -e &quot;\nDisk Usage:&quot;<br>df -h<br>echo -e &quot;\nLoad Average:&quot;<br>uptime<br>echo -e &quot;\nTop CPU Processes:&quot;<br>ps aux - sort=-%cpu | head -4</pre><p>Save this as health_check.sh, make it executable with <strong>chmod +x health_check.sh</strong>, and run it with <strong>./health_check.sh</strong>. Now you’ve got a one-command server check! You can try this with the practice environment you set up earlier!</p><h3>Man Pages: Your Local Documentation</h3><p>When you’re stuck, don’t immediately jump to Google. Try <strong>man</strong> command first. For example:</p><pre>man grep<br>man find<br>man systemctl</pre><p>The man pages might look intimidating, but they’re incredibly detailed. I usually jump to the “EXAMPLES” section first — it’s often all you need. Once you’re comfortable navigating man pages, you’ll find they can be more efficient than sifting through multiple web search results.</p><h3>What’s Next?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/571/0*_bLiRjNwapZwpB6t.jpg" /></figure><p>Here’s the thing about Linux — you never really “finish” learning it. I’m still discovering new commands and tools after 4 years. Instead of trying to memorize everything:</p><ol><li>Practice the basics until they’re muscle memory</li><li>Get comfortable reading man pages and documentation</li><li>Start building your own scripts for repeated tasks</li><li>Keep a cheat sheet (I still have mine pinned in Slack)</li></ol><blockquote>Remember: In real work, nobody expects you to memorize everything. The skill is in knowing what’s possible and where to find the right command when you need it.</blockquote><p>My favorite resources for learning more:</p><ul><li>Codecademy: <a href="https://www.codecademy.com/learn/introduction-to-linux">Introduction to Linux</a></li><li><a href="https://www.boot.dev/courses/learn-linux">boot.dev</a></li><li>Your own projects (seriously, spin up some personal projects on your <strong>EC2</strong> instance)</li></ul><blockquote>Final tip: Don’t just copy-paste commands. Try to understand what each part does. It’ll save you from some embarrassing (or dangerous) mistakes in production.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d9ae5233b333" width="1" height="1" alt=""><hr><p><a href="https://medium.com/coodev/mastering-linux-for-devops-from-basic-commands-to-production-troubleshooting-d9ae5233b333">Mastering Linux for DevOps: From Basic Commands to Production Troubleshooting</a> was originally published in <a href="https://medium.com/coodev">CooDev</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introduction to DevOps / CooDev]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/coodev/introduction-to-devops-coodev-299ee745c37d?source=rss----560f2d787c4c---4"><img src="https://cdn-images-1.medium.com/max/2400/1*ORvQpZdPX1h8vMaorQS6VA.jpeg" width="2400"></a></p><p class="medium-feed-snippet">Hello, folks!</p><p class="medium-feed-link"><a href="https://medium.com/coodev/introduction-to-devops-coodev-299ee745c37d?source=rss----560f2d787c4c---4">Continue reading on CooDev »</a></p></div>]]></description>
            <link>https://medium.com/coodev/introduction-to-devops-coodev-299ee745c37d?source=rss----560f2d787c4c---4</link>
            <guid isPermaLink="false">https://medium.com/p/299ee745c37d</guid>
            <category><![CDATA[devops-introduction]]></category>
            <category><![CDATA[devopsfreecourse]]></category>
            <category><![CDATA[devops-hands-on]]></category>
            <category><![CDATA[devops-practice]]></category>
            <category><![CDATA[devops-online-course-usa]]></category>
            <dc:creator><![CDATA[Kanat Akylson]]></dc:creator>
            <pubDate>Fri, 10 Jan 2025 21:29:57 GMT</pubDate>
            <atom:updated>2025-01-10T21:29:57.602Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Free DevOps Course in 2025]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/coodev/free-devops-course-in-2025-c57b825e1efa?source=rss----560f2d787c4c---4"><img src="https://cdn-images-1.medium.com/max/1024/1*lY7CrJvH6Tu1bQXUzg5wcA.png" width="1024"></a></p><p class="medium-feed-snippet">Hello everyone!</p><p class="medium-feed-link"><a href="https://medium.com/coodev/free-devops-course-in-2025-c57b825e1efa?source=rss----560f2d787c4c---4">Continue reading on CooDev »</a></p></div>]]></description>
            <link>https://medium.com/coodev/free-devops-course-in-2025-c57b825e1efa?source=rss----560f2d787c4c---4</link>
            <guid isPermaLink="false">https://medium.com/p/c57b825e1efa</guid>
            <category><![CDATA[devops-for-beginners]]></category>
            <category><![CDATA[devopsfreecourse]]></category>
            <category><![CDATA[devops-courses]]></category>
            <category><![CDATA[free-online-course]]></category>
            <category><![CDATA[online-devops-course]]></category>
            <dc:creator><![CDATA[Kanat Akylson]]></dc:creator>
            <pubDate>Sat, 04 Jan 2025 14:17:49 GMT</pubDate>
            <atom:updated>2025-01-04T14:07:20.374Z</atom:updated>
        </item>
    </channel>
</rss>