Mastering Shell Scripting with Bash Certification

Frustrated chasing Docker commands buried in history? One line pulls them all. ⚡ Command: `history | grep 'docker' | tail -20` history prints your shell's command history. grep 'docker' filters lines containing docker. tail -20 shows the last 20 matches, giving the most recent Docker actions. Tip: grep -i 'docker' for case-insensitive results. Real use case: you're debugging a late-night deployment and need the last 20 Docker commands to reconstruct steps. This list lets you reproduce fixes or roll back precisely. This one-liner hands you that list fast, ready to paste into a ticket. Why it matters: small, fast, auditable. The terminal becomes your memory and your workflow engine. Run it right now. Tell me what you find. #linux #terminal #bash #commandline #devops #sysadmin #programming #opensource #productivity #coding #softwareengineering #docker #automation #workflow #learncoding

🚀 Day 18 – Shell Scripting Level Up! Today I focused on writing cleaner, safer, and reusable shell scripts — a big step from basic scripting to real-world usage 💻 What I learned: ✔️ Writing and calling functions for reusable code ✔️ Using set -euo pipefail for safer scripts ✔️ Handling return values & local variables ✔️ Building a complete system info script One important takeaway: Using set -euo pipefail makes your scripts more reliable and production-ready by preventing silent failures. Key Learnings: Functions = Cleaner & reusable code Strict mode = Safer & error-free scripts Check out my work:https://lnkd.in/g4TvriXU #90DaysOfDevOps #DevOpsKaJosh #TrainWithShubham #DevOps #ShellScripting #Linux #Automation #Scripting #LearningInPublic #TechJourney #Cloud #Programming #CareerGrowth #ITJobs #Developers #CodeNewbie

🚀 Day 21/90 – DevOps Learning Journey Today I created my own Shell Scripting Cheat Sheet after completing multiple hands-on scripting tasks. 🔹 What I covered • Bash basics, variables, arguments • If-else, loops, functions • File checks and logical operators • Powerful tools: grep, awk, sed, sort, uniq • Real-world one-liners for log analysis • Error handling using set -euo pipefail 💡 Key Learning Writing a cheat sheet forced me to organize concepts clearly — Now I can quickly debug scripts without searching documentation every time. This will be my go-to reference during real DevOps tasks 🚀 Consistency is building confidence day by day 💪 #90DaysOfDevOps #DevOpsKaJosh #TrainWithShubham #ShellScripting #Linux #Automation

I broke my laptop's Python environment 3 times in one month. Different projects needed different versions. One pip install would quietly destroy another project. Then I learned Docker — and everything changed. Here's what Docker actually does (no jargon): → It wraps your app + its dependencies into a box called a container → That box runs the same on your laptop, your teammate's Mac, and a Linux server → You stop saying "it works on my machine" — because it works everywhere My first Dockerfile was 5 lines: ``` FROM python:3.11 WORKDIR /app COPY . . RUN pip install -r requirements.txt CMD ["python", "app.py"] ``` That's it. No more environment disasters. I'm a CS student learning DevOps in public — this was my week 1 win. Have you had your environment broken by dependency conflicts? How did you fix it? #Docker #DevOps #LearnInPublic #CS #BackendDev

Day 21 of learning and practicing DevOps 🔁 Today was a #revision + consolidation day — built my own Shell Scripting Cheat Sheet I focused on organizing everything from the last few days for shell scripting Covered: • Script basics (shebang, variables, arguments) • Conditions, loops, and functions • Text processing tools like grep, awk, sed • Error handling (set -e, $?, debugging) • Useful one-liners I can use in real scenarios many more...... Important part: Writing a cheat sheet made me realize what I actually understand vs what I just “used once”. This cheat sheet will be something I can refer to anytime during scripting or debugging. Here are my notes: https://lnkd.in/gzXn3Jrv 📍 #DevOps #Linux #ShellScripting #Automation #LearningInPublic #90DaysOfDevOps #TrainWithShubham

Many times while working on projects, we open CMD, PowerShell, or Git Bash… and suddenly forget the most basic commands. Things like: cd .. ls mkdir pwd rm clear These commands are simple, but they are used almost daily in development. So I created a small 2-page PDF cheat sheet containing the most important basic terminal commands for: CMD PowerShell Git Bash If you're a beginner in coding, Git, or development, this will save you time and confusion. Download the PDF, keep it saved, and try practicing these commands once. It will make your workflow faster and more confident. #Git #GitBash #PowerShell #CMD #Terminal #Developer #Programming #Coding #SoftwareDevelopment #Learning #ComputerScience #Tech #Beginners #Productivity

No more PR guesswork. git diff --stat is your quiet auditor. 🔥 git diff --stat It compares your working tree to HEAD by default and lists per-file insertions and deletions plus a totals line. For a specific pair of commits use HEAD~1..HEAD. You're reviewing a feature PR that touches 150 files. git diff --stat reveals heavy churn in src/ and tests, light changes in docs. Small time savings compound across teams. The terminal becomes a lightweight dashboard for risk and impact. 🐧 What command would you pair this with? Drop it below. #linux #terminal #git #diffstat #devops #sysadmin #commandline #automation #productivity #coding #opensource #buildinpublic #ci #pr

Day 5 of Shell Scripting — Log Analysis Like a Real DevOps Engineer [Writing this at 4:03 PM IST] Most people learn commands. Today I learned to think in pipelines. Day 5 was all about grep, awk, and sort — and how combining them turns raw log files into actual intelligence. What I practiced on a real app.log file: grep — filtered errors, debugs, warnings with -i (case insensitive), -n (line numbers), -c (count), -v (exclude). Found 7 ERROR entries and 4 DEBUG entries instantly. awk — extracted specific fields from those filtered lines. Timestamp + service component in one clean output. sort — sorted that output by service name using -k2 to group all database, api, auth errors together. The final command that clicked for me: grep "ERROR" app.log | awk '{print $2, $4}' | sort -k2 Three tools. One pipeline. Instant clarity on which service is failing most. This is exactly what you need when you're on-call at 2 AM and a production system is throwing errors. No GUI. Just you, the terminal, and your grep flags. Day 5 done. Pipeline thinking unlocked. 🔥 #DevOps #Linux #ShellScripting #BashScripting #100DaysOfCode #DevOpsJourney #Korelium

#️⃣ 1️⃣ Get Intimate with Your Shell 🐧 0️⃣ If you're doing any serious scripting, there’s a hard truth you need to accept: you can't just copy-paste your way through forever. You need to intimately know your shell. 🐚 1️⃣ I see a lot of engineers dive into writing automation without checking what environment they're actually executing in. 2️⃣ Is it bash ❓ ➡️ Probably. It’s the undisputed workhorse of the Linux world. But if you’re doing local dev on a modern Mac, you’re likely dropping into zsh. And if you're working with lightweight Docker containers (like Alpine) or legacy systems, you might find yourself face-to-face with sh—the direct lineage of the ancient, original Thompson shell. ⁉️ Why does this matter ❔ Because portability is everything. ➡️ What works effortlessly in bash (like arrays or specific parameter expansions) will often blow up your script in sh. If you're writing automation for CI/CD pipelines, cron jobs, or container entrypoints, assuming you have bash when you only have a barebones sh is a guaranteed recipe for a failed build. 3️⃣ Take the time to understand the nuances: 👉 Check your shebangs (#!/bin/bash vs #!/bin/sh). 👉 Know when to write strict, POSIX-compliant code for maximum portability across environments. 👉 Know when it’s safe to lean into the rich, modern features of zsh or bash. 4️⃣ Mastering your shell doesn't just make you a faster typist; it makes your scripts vastly more robust, your pipelines more reliable, and your debugging sessions a lot shorter. ⁉️ What’s your daily driver ❔ Are you team Bash, Zsh, or do you prefer something entirely different like Fish? ‼️ Let me know below. 👇 #Linux #DevOps #ShellScripting #Bash #Zsh #Automation #SoftwareEngineering #TechTips

Day 20 of learning and practicing DevOps 🔁 Worked on scripting project — building a log analyzer and report generator Worked on: • Reading and validating log file input • Counting errors (ERROR, Failed) using grep • Extracting critical events with line numbers • Finding top 5 recurring errors using awk, sort, uniq • Generating a structured report file • Archiving processed logs automatically Important part: Instead of manually reading logs, I built a script that analyzes everything and gives a summary in seconds. Learning today--> logs tell the story turning raw logs into useful insights. Here are my notes: https://lnkd.in/ga8xUT6U 📍 #DevOps #Linux #ShellScripting #Automation #LogAnalysis #LearningInPublic #90DaysOfDevOps #TrainWithShubham