Day 21 of #90DaysOfDevOps For the past few days, I’ve been actively practicing Bash scripting — learning step by step, breaking things, fixing them, and understanding how commands actually behave in real scenarios. During this process, I noticed a pattern… I kept revisiting the same commands again and again. Instead of searching every time, I thought — why not create something simple and useful for myself? So today, I built a Bash Cheat Sheet with 20 essential commands that I find myself using almost daily. This includes: - Running scripts & handling variables - Taking user input & passing arguments - File and directory checks - Conditions, loops, and functions - Powerful text processing using grep, sed, and awk - Log monitoring & disk usage checks This small effort really helped me organize my learning and made things much quicker during practice. Still a long way to go, but building things like this makes the journey more practical and enjoyable. If you're learning Bash or DevOps, try creating your own cheat sheet — it helps more than you think. Link to the complete cheatsheet https://lnkd.in/dzhgD8Uf #Bash #Linux #Scripting #LearningInPublic #90DaysOfDevOps #DevOpsKaJosh #TrainWithShubham
Bash Cheat Sheet for DevOps Essentials
More Relevant Posts
-
🚀 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
To view or add a comment, sign in
-
-
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
To view or add a comment, sign in
-
🐳 Getting Hands-On with Docker! Over the past few days, I've been diving deep into Docker — and honestly, it's been a game-changer in how I think about building and deploying applications. From pulling images to running containers, managing volumes to pushing to Docker Hub — every command I learned made me realize how powerful containerization really is. 💡 So I put together this Docker Cheat Sheet covering all the essential commands — images, containers, networks, volumes, Dockerfile, and more — in one place! Whether you're just starting out or need a quick reference, I hope this helps your DevOps journey too. 🚀 📌 Save this post so you never forget these commands! 💬 Drop a comment if you found this helpful or if I missed any command! 🔁 Repost to help others in the community! #Docker #DevOps #Linux #Containers #CloudNative #Programming #LearningInPublic #TechCommunity #OpenSource
To view or add a comment, sign in
-
-
It’s been a while since my last update on my DevOps journey with CoderCo — but I’ve been putting in the work behind the scenes. Since completing Linux Fundamentals, I’ve been diving into Bash scripting, and things are starting to click. Some of what I’ve been learning: - Writing Bash scripts to automate simple tasks - Using tools like "awk" and "grep" to process data - Understanding exit codes and error handling - Working with "set -e" and "set -u" to make scripts safer and more reliable It’s a different feeling now — less “copying commands” and more actually understanding what’s happening. Still a long way to go, but definitely seeing progress. Next focus: building small scripts and applying this in real scenarios. If anyone has beginner-friendly scripting projects or tips, I’d appreciate it. #DevOps #Linux #Bash #Automation #LearningJourney
To view or add a comment, sign in
-
📜Learning bash scripting taught me something I didn't expect: The gap between understanding something and using something is massive. You can read about variables and functions all day. But the real progress happens when you: → Apply the theory in isolation (write the function, test it, break it) → Connect the concepts (pass parameters, capture input, handle logic) → Build something end-to-end (a real script that solves a real problem) 👇Below is a script I put together that sorts all .txt files in a directory by size, smallest to largest, with input validation built in. Is it the most efficient script? Probably not. But that's the point, efficiency comes with practice, and you can't refine what you haven't built yet! Most people stop at step one and wonder why it's not sticking. Build something, even something small. That's where it lands. What's a skill you learned by just building with it? 💻 #Bash #Scripting #Linux #Tech #DevOps
To view or add a comment, sign in
-
-
🚀 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
To view or add a comment, sign in
-
DevOps Zero to Job-Ready – Day 4/180 | Linux Text Processing Today I focused on something that’s actually used a lot in real DevOps work — text processing. What I explored: Searching logs using grep Case-insensitive search (-i) Finding exact lines (-n) Using pipes (|) to combine commands What I realized: In real environments, logs can be huge. You can’t manually scroll and find issues. You need to search smartly. Debugging failed deployments Investigating production issues Sharing today’s notes as well for anyone learning along. I’m also organizing all structured notes, real-world scenarios, and project-based learning content on www.engidock.com — useful if you want a more guided DevOps learning path. Next: Bash scripting basics Trying to stay consistent with this series — one step at a time. #EngiDock #DevOps #Linux #LearningInPublic #Debugging
To view or add a comment, sign in
-
🚀 𝗨𝗻𝗱𝗲𝗿𝘀𝘁𝗮𝗻𝗱𝗶𝗻𝗴 𝗔𝗻𝘀𝗶𝗯𝗹𝗲 𝗠𝗼𝗱𝘂𝗹𝗲𝘀: 𝗿𝗮𝘄 𝘃𝘀 𝗰𝗼𝗺𝗺𝗮𝗻𝗱 𝘃𝘀 𝘀𝗵𝗲𝗹𝗹 When starting with Ansible, many people get confused between 𝗿𝗮𝘄, 𝗰𝗼𝗺𝗺𝗮𝗻𝗱, and 𝘀𝗵𝗲𝗹𝗹 modules. At first, they look similar… but each has a specific purpose. Let’s break it down simply 👇 🔹 𝗿𝗮𝘄 𝗺𝗼𝗱𝘂𝗹𝗲 👉 Executes commands directly over SSH 👉 Does NOT require Python on the remote machine 👉 Mostly used for bootstrapping systems ⚠️ Bypasses Ansible features, so use it carefully 🔹 𝗰𝗼𝗺𝗺𝗮𝗻𝗱 𝗺𝗼𝗱𝘂𝗹𝗲 👉 Runs commands without using a shell 👉 More secure and predictable 👉 Recommended for most use cases ✔️ No shell operators like `|`, `>`, `&&` 🔹 𝘀𝗵𝗲𝗹𝗹 𝗺𝗼𝗱𝘂𝗹𝗲 👉 Executes commands through a shell 👉 Supports pipes, redirects, and operators ✔️ Useful when you need complex commands ⚠️ Slightly less secure than command module 💡 𝗦𝗶𝗺𝗽𝗹𝗲 𝗿𝘂𝗹𝗲 𝘁𝗼 𝗿𝗲𝗺𝗲𝗺𝗯𝗲𝗿: ➡️ Use 𝗰𝗼𝗺𝗺𝗮𝗻𝗱 by default ➡️ Use 𝘀𝗵𝗲𝗹𝗹 when you need shell features ➡️ Use 𝗿𝗮𝘄 only when Python is not available 🔥 Mastering these small differences makes your automation more reliable and production-ready. #Ansible #DevOps #Automation #Linux #Cloud #Learning #BeginnerFriendly
To view or add a comment, sign in
-
-
Just found a really cool way to practice Kubernetes without turning it into another dry checklist of commands. K8sQuest makes learning Kubernetes feel more like a challenge-based game: you get broken scenarios, investigate what’s wrong, and fix them like you would in a real cluster. That’s the kind of practice that actually sticks. What I like about it: - hands-on troubleshooting instead of passive theory - progressive challenges across core Kubernetes topics - a more engaging way to build real debugging habits - useful for both beginners and engineers who want extra lab practice This is the type of project that can make Kubernetes learning much less intimidating and much more practical. Repo: https://lnkd.in/dDCy4uyj Definitely worth checking out if you’re into: #Kubernetes #DevOps #CloudNative #PlatformEngineering #SRE #OpenSource #K8s #LearningByDoing
To view or add a comment, sign in
-
At some point, running commands stops being enough. You start asking: why am I doing this more than once? I’ve completed the Introduction to Shell Scripting Basics certification from CodeSignal as part of the Mastering Shell Scripting with Bash path. This stage marked a shift from simple execution to structured control—moving from typing commands to building logic that can make decisions and act independently. I worked through variable manipulation, including string handling and arithmetic expansion $((...)), while also navigating Bash’s strict whitespace rules that demand precision. I implemented conditional logic using if-elif-else structures with both numeric and string operators, built and iterated through arrays using different loop strategies, and created reusable functions using positional parameters ($1, $2) and $@ to handle multiple inputs efficiently. The key takeaway is straightforward: automation starts with how well you structure small things. This foundation is what enables everything else in system scripting and DevOps. #ShellScripting #Bash #Linux #Automation #DevOps #SoftwareEngineering #BackendDevelopment #Programming #Coding #TechSkills #ContinuousLearning #Developers #Engineering #CommandLine #Productivity #Scripting #Unix #TechCareer #CodeSignal #brittonnetic CodeSignal https://lnkd.in/dAB9TMRF
To view or add a comment, sign in
-
Explore content categories
- Career
- Productivity
- Finance
- Soft Skills & Emotional Intelligence
- Project Management
- Education
- Technology
- Leadership
- Ecommerce
- User Experience
- Recruitment & HR
- Customer Experience
- Real Estate
- Marketing
- Sales
- Retail & Merchandising
- Science
- Supply Chain Management
- Future Of Work
- Consulting
- Writing
- Economics
- Artificial Intelligence
- Employee Experience
- Workplace Trends
- Fundraising
- Networking
- Corporate Social Responsibility
- Negotiation
- Communication
- Engineering
- Hospitality & Tourism
- Business Strategy
- Change Management
- Organizational Culture
- Design
- Innovation
- Event Planning
- Training & Development