Forem: Abdul Rub

Day 3-4: Shell Scripting – Automating Your DevOps Workflow 🐚⚡

Abdul Rub — Sun, 06 Apr 2025 13:17:46 +0000

Welcome back to my #DevOpsJourney! In Day 3-4, we’re diving into one of the most powerful tools in any DevOps toolkit: Shell Scripting. Automating routine tasks, and streamlining processes—these are just a few of the things we can achieve with shell scripts.

Let's break down the basics and see how you can unlock the power of automation in your workflows.

Think of shell scripting like a recipe book 📚. By writing the right instructions, you can automate time-consuming tasks and bring efficiency to your operations.

🖥️ 1. Getting Started with Shell Scripting

A shell script is just a file with a sequence of terminal commands. When run, the shell executes them in order.

Create Your First Script:

Add this line at the top to specify the shell:

Add your first command:

Make it executable:

Run it:

Boom! You've just created your first working script 🎉

⚙️ 2. Control Flow & Logic in Shell Scripting

Shell scripts become powerful when you add logic like conditionals and loops.

If-Else Condition:

For Loop:

While Loop:

📜 3. Advanced Techniques

Once We’ve nailed the basics, start using variables, functions, redirections, and scheduling.

Variables:

Functions:

Redirecting Output:

Redirecting Errors:

Cron Job for Scheduling:

Edit crontab:

Example to run a script daily at midnight:

🔧 4. Handy Shell Commands

Some useful commands often used in automation:

*grep * – Search patterns in files

*sed *– Find and replace in files

*awk *– Process text and data

tar – Create backups

📈 5. Real-World Use Cases in DevOps

✅ Automated Deployments – Script your deployments for consistency
✅ System Monitoring – Check disk usage, CPU, memory, etc.
✅ Backup Automation – Schedule daily or weekly backups
✅ Log Management – Analyze and filter logs programmatically

🏁 Wrapping Up

Shell scripting is a must-have skill for anyone diving into DevOps.
It brings automation, speed, and precision to your daily tasks and long-term projects.

Start simple. Automate small tasks. Then scale your knowledge to tackle bigger challenges.

What’s one script you’ve written that saved you tons of time?
Let’s connect and share ideas! 💬

Day 2: Linux Basics – Essential Commands (Part 2) 🐧⚡

Abdul Rub — Wed, 02 Apr 2025 19:37:21 +0000

Welcome back to my #DevOpsJourney! In Day 1, we covered system monitoring, networking, and file management. Today, we’ll master process control, text processing, and automation tools—the secret sauce of DevOps efficiency!

Think of these commands like kitchen gadgets 🍳—each saves time and effort, so you can focus on cooking up great infrastructure!

⚙️ 4. Process Management – Controlling Running Apps

16 . kill – The Process Terminator

What it does: Stops misbehaving processes.

Real-life analogy: Force-quitting a frozen app on your phone.

When to use:

When a program hangs or consumes too much CPU.
Pro Tip: Find PIDs with ps aux | grep .

17 . killall – Bulk Terminator

What it does: Kills processes by name.

Real-life analogy: Turning off all lights in a room with one switch.

When to use:

When multiple instances of a service need restarting.

18 . bg & fg – Multitasking Wizards

What they do:

bg resumes a paused job in the background.

fg brings it back to the foreground.

Real-life analogy:

bg → Minimizing YouTube to work.

fg → Bringing it back to watch.

When to use:

19 . jobs – Background Task Manager

What it does: Lists background/suspended jobs.

Real-life analogy: Checking your to-do list sticky notes.

When to use:

Managing long-running tasks (e.g., backups).

📜 5. Text Processing – Data Manipulation

20 . sed – The Text Surgeon

What it does: Finds/replaces text in files or streams.

Real-life analogy: Find & Replace All in a Word doc.

When to use:

Editing config files in bulk.
Removing empty lines: sed '/^$/d' file.txt.

awk – The Data Scientist

What it does: Extracts and processes structured data (e.g., logs, CSVs).

Real-life analogy: Filtering Excel columns for analysis.

When to use:

Parsing server logs.
Calculating sums: awk '{sum+=$1} END {print sum}' data.txt.

22 . cut – The Column Cutter

What it does: Extracts specific columns from text.

Real-life analogy: Cutting coupons from a newspaper.

When to use:

Processing CSV/TSV files.

23 . tr – The Character Translator

What it does: Replaces/deletes characters.

Real-life analogy: Converting lowercase to uppercase with a button.

When to use:

Sanitizing inputs (e.g., removing spaces).

🔗 6. File Linking & Archives

24 . ln – The Shortcut Creator

What it does: Creates hard/soft links (like Windows shortcuts).

Real-life analogy:

Hard link: A mirror (same file, two names).

Soft link: A GPS shortcut (points to original).

When to use:

Linking config files across directories.

25 . tar – The File Packer

What it does: Combines files into a tarball (.tar.gz).

Real-life analogy: Zipping clothes into a suitcase.

When to use:

Creating backups.

26 . zip/unzip – Cross-Platform Archiver

What it does: Compresses to .zip format.

Real-life analogy: Packing files for email attachments.

When to use:

Sharing files with Windows users.

Day 1: Linux Basics – The Power of Commands 🐧💻

Abdul Rub — Wed, 02 Apr 2025 18:43:55 +0000

Welcome back to my #DevOpsJourney! 🚀 Yesterday, we explored what DevOps is, why cloud computing is a game-changer, and why Linux is the backbone of DevOps. Today, we dive into Linux commands—the essential tools that make Linux a powerhouse for DevOps.

Think of Linux commands like kitchen tools 🍳—each has a specific purpose, and mastering them lets you cook up amazing automation, troubleshooting, and system management recipes!

📊 1. System Monitoring & Resource Management

top – The Real-Time System Monitor

What it does: Displays CPU, memory, and process stats.

Real-life analogy: Like checking your car’s dashboard while driving (speed, fuel, engine health).

When to use:

When your server is slow.
To find which process is consuming max CPU/RAM.

2 . htop – Supercharged top

What it does: Colorful, interactive process viewer.

Real-life analogy: Upgrading from a bicycle speedometer to a Tesla’s touchscreen.

When to use:

When you need a clearer view of processes.
To kill processes with F9.

3 . ps – Process Snapshot

What it does: Lists running processes.

Real-life analogy: Taking a roll call in a classroom.

When to use:

Debugging crashes.
Checking if a service (e.g., MySQL) is running.

4 . free – Memory Checker

What it does: Shows RAM and swap usage.

Real-life analogy: Checking your wallet (RAM) and emergency cash (swap).

When to use:

When apps crash due to "Out of Memory" errors.

5 . df – Disk Space Analyzer

What it does: Shows disk usage per partition.

Real-life analogy: Checking storage on your phone ("Is there space for an update?").

When to use:

Before installing large software.
If your server logs complain about "No space left".

6 . du – Directory Space Hog Finder

What it does: Checks file/folder sizes.

Real-life analogy: Finding which app is eating your phone’s storage.

When to use:

Locating large log files to clean up.

7 . uptime – Server Lifespan Check

What it does: Shows how long the system has been running.

Real-life analogy: Checking your laptop’s uptime since last reboot.

When to use:

Debugging unexpected reboots.

🌐 2. Networking – The Digital Highway

8 . ping – Network Connectivity Test

What it does: Checks if a server/website is reachable.

Real-life analogy: Knocking on a neighbor’s door to see if they’re home.

When to use:

Testing if the internet works.
Troubleshooting "Server not found" errors.

9 . curl – API/Data Fetcher

What it does: Transfers data via URLs (APIs, downloads).

Real-life analogy: Ordering food via an app (GET/POST requests).

When to use:

Testing REST APIs.
Downloading files in scripts.

10 . netstat – Network Statistician (Legacy, use ss instead)

What it does: Lists active connections and ports.

Real-life analogy: Checking who’s calling your phone.

When to use:

11 . ss – Modern netstat

What it does: Faster socket statistics.

When to use:

Debugging "Port already in use" errors.

12 . traceroute – Network Path Tracer

What it does: Maps the route packets take to a host.

Real-life analogy: Tracking your pizza delivery route.

When to use:

Diagnosing slow network speeds.

📂 3. File & Directory Management

13 . ls – The Folder Explorer

What it does: Lists files/directories.

Real-life analogy: Opening a drawer to see what’s inside.

When to use:

Always. Basic navigation.

14 . grep – The Text Detective

What it does: Searches for patterns in files.

Real-life analogy: Ctrl+F in a document.

When to use:

Parsing logs.
Filtering command outputs.

15 . chmod – Permission Manager

What it does: Changes file permissions (read/write/execute).

Real-life analogy: Setting a locker combo.

When to use:

When a script won’t run due to "Permission denied".

Day 0: Learning DevOps – The Journey Begins 🌱

Abdul Rub — Tue, 01 Apr 2025 12:10:18 +0000

It all started with a simple question: What is DevOps?
Imagine you're planning a road trip. You’ve got the perfect destination in mind, the best route mapped out, but there’s one problem—different teams are handling the map, the car, the fuel, and the itinerary. As you drive, everyone’s working in silos, and communication is choppy. The trip could be delayed, rerouted, or worse—cause frustration.

Now, picture DevOps as the solution to this problem. Instead of separate teams working in isolation, DevOps brings them together. It’s the bridge between the development team 🧑‍💻 (the ones who build the road) and the operations team 🛠️ (the ones who ensure the road is safe and ready to use). DevOps allows everyone to work as one cohesive unit, with the ultimate goal of making the journey smooth and continuous.

What is DevOps? 🤔
DevOps is a combination of development (Dev) and operations (Ops), aiming to shorten the software development lifecycle. It emphasizes collaboration, automation, continuous integration, and feedback. Think of it as a symbiotic relationship between the builders (developers) and maintainers (operations) of a product. Instead of working in isolation, both teams now collaborate, continuously integrate, and deploy code, all while ensuring that the system is stable and scalable.

In real life, think of it as the assembly line in a car factory 🚗. Developers build the car’s parts (features), and operations handle the assembly, testing, and delivery (deployment). They work in tandem so the car gets built and reaches the customer faster and without delays.

The DevOps Mindset 🧠💡
So, why isn’t the DevOps journey as simple as it sounds? Well, it’s not just about tools and processes; it’s about mindset. In DevOps, the mindset is about seeing the bigger picture, where collaboration, trust, and shared responsibility are key. It’s not just a “I code, you deploy” world anymore. It’s about fostering a culture where both development and operations teams are equally invested in the product’s success.

It’s like baking a cake 🎂. The developer might make the batter (code), but the operations team handles the oven and decorations (deploying and maintaining the system). Both teams need to communicate well, adjust the temperature (optimize processes), and share feedback to create the perfect cake (working software).

A DevOps mindset encourages constant learning and improvement. You're always looking at what went well and how you can make the process faster, better, and smoother. It's like refining your recipe after every bake to make the next one even better.

What is Cloud? ☁️
Before we dive into why cloud is a game-changer for DevOps, let's first understand what it is. The cloud is a vast network of servers that allows us to store and access data, host applications, and run various services over the internet 🌍. Instead of relying on physical servers (which take up space and are expensive to maintain), we rent virtual servers and services hosted by companies like Amazon (AWS), Microsoft (Azure), and Google (Google Cloud). The cloud is like renting a room in a hotel 🏨 instead of owning a house. You only pay for what you use, and if you need more space, you can easily upgrade.

For DevOps, cloud platforms provide the flexibility to spin up environments and scale applications on-demand. It makes setting up, deploying, and testing applications faster. No need for bulky hardware setups or worrying about infrastructure—it's all taken care of in the cloud.

Why is Cloud Better? 🚀
Let’s consider this with a real-life analogy. Imagine trying to host a dinner party at home 🏠. You need to prepare the food, set up tables, and manage everything yourself. If 10 guests show up, you're okay. But what if 50 guests suddenly arrive? That’s a lot of extra preparation!

Now, what if you could simply call a caterer 🍴 who already has all the food, tables, and seating arrangements ready? And if more guests arrive, they can just bring in more food and seating. The cloud is like that caterer. It provides you with scalable infrastructure, resources, and services without the hassle of managing everything on your own. Whether you need a little or a lot, cloud services can scale up or down to meet your needs.

Linux: The Powerhouse Behind DevOps 🐧💪
Now, let’s talk about Linux. As you embark on your DevOps journey, you’ll soon realize that Linux is the operating system that drives many of the tools and applications in the DevOps pipeline. Why? Because Linux is open-source, lightweight, stable, and secure—exactly what DevOps needs.

Think of Linux as a Army knife 🔪—compact, versatile, and reliable. You can use it for a variety of tasks, from running servers to hosting applications, automating tasks, or managing databases. It’s like the foundation of a house 🏡—strong, reliable, and built to last.

Why Linux is Better for DevOps 🏅
Linux is the preferred operating system for DevOps for several reasons:

Customization 🛠️: Linux allows you to customize the system according to your needs. It’s like tailoring a suit to fit you perfectly. You can install only the necessary software, keeping it lean and efficient.
Open-Source Community 🌍: Since Linux is open-source, there’s a massive community of developers constantly improving it. If you run into an issue, chances are someone else has already solved it. It’s like having an army of helpers always available to lend a hand.
Security 🔒: Linux has a reputation for being secure. With regular patches and updates, it’s less prone to viruses and attacks. Imagine a well-guarded castle with tight security where only authorized people are allowed in.
Compatibility 🖥️: Most of the tools used in DevOps (like Docker, Kubernetes, and Jenkins) were either built for Linux or work better on Linux. It’s like buying a car that’s built to run on premium fuel—it just works better.
Stability ⚙️: Linux servers are known for running for years without crashing or needing a restart. It’s like owning a reliable old car that keeps going strong even after many years of use.

The Road Ahead 🌄
So, this is where we begin our DevOps journey. It’s like setting out on an adventure 🚀. We've learned about what DevOps is, the mindset behind it, why cloud computing is the key to flexibility, and why Linux is the operating system of choice for many DevOps professionals.

Remember, DevOps isn’t just a set of tools or a process—it's a culture, a mindset, and a way of continuously improving. As we dive deeper into DevOps, we'll learn more, experiment with new tools, and build processes that will help us deploy software faster and more efficiently.