Shriyanshi Soni’s Post

Day 10/100 — Website Backup Script 📦🖥️ Wrote a bash script to automatically zip a website directory, store it locally, and securely transfer it to a remote storage server using passwordless SCP. 🔑 Key Takeaway: A good backup script isn't just about copying files — it's about structure, permissions, passwordless auth, and zero manual intervention. Automate it right the first time. Day 10 ✅ | 90 more to go! #DevOps #Linux #BashScripting #Automation #Backup #KodeKloud #100DaysOfDevOps #LearningInPublic

From ssh to ansible-playbook. 🔄 Today marks the transition from manually configuring every VM to letting Ansible do the heavy lifting. Setting up a Node server environment used to take 20 minutes of manual typing; now, it's a single command. The learning curve with SSH keys and Netplan was real, but the efficiency gain is even more real. 💻✨ Anyone else remember the first time they got an Ansible ping to succeed? It's the little victories. #Ansible #Linux #Tech #DevOpsEngineer #CloudComputing

📅 Day 2 – Linux File System 📂 Today I explored how Linux organizes everything internally. Here’s a quick summary: 🔹 Root Directory / Starting point of the entire system 🔹 Paths Absolute Path → starts from / (full path) Relative Path → starts from current directory 🔹 Key Directories /home → user files /etc → configuration files /var → logs & variable data 💡 Understanding this feels like seeing the system from inside — things are slowly making sense! Q: Difference between absolute and relative path? Answer: Absolute path starts from root / and gives full location Relative path starts from current directory and is shorter #DevOps #Linux #LearningJourney #Day2 🚀

🐧 Linux File System Explained (Where Everything Lives) In Linux, everything is organized — if you understand the structure, you troubleshoot faster. 📁 Root Directory (/) The starting point of the Linux file system. Everything branches from here. ⚙️ Important Directories 📂 "/etc" → Configuration files 📂 "/var" → Logs and variable data 📂 "/home" → User directories 📂 "/bin" → Essential commands 📂 "/usr" → Installed software 📂 "/tmp" → Temporary files 📜 Log Location "/var/log" → System and application logs 🧠 Why It Matters • Easier troubleshooting • Faster navigation • Better system understanding 🚀 Real Example Server issue? Check logs in "/var/log" before anything else. 💡 Key Insight Linux is not random — it’s a well-structured system. #Linux #DevOps #SystemAdmin #FileSystem #CloudEngineer #LinuxCommands #SRE

My backup script worked… but only after I fixed the user context. Day 10 of #100DaysOfDevOps ✅ Today’s task was to write a Bash script that zips a blog directory, stores it locally, and transfers it to another server using SCP — without any password prompt. The setup involved installing zip, creating the script, and configuring passwordless SSH. The key learning was around who actually runs the script. Since the script runs as steve, the SSH keys also had to be generated and configured for steve, not root. Once that was set correctly, the backup and transfer worked seamlessly. Day 10 complete. 90 to go 🚀 Full solution on GitHub 👇 https://lnkd.in/dk8Frue7⁠� #DevOps #Linux #BashScripting #Automation #SSH #100DaysOfDevOps #LearningInPublic #SRE

🚀 What is Cron Job in Linux? (Automate your tasks easily) When I started working on Linux, I used to run tasks manually again and again. Then I discovered Cron Jobs 👇 💡 A cron job is used to schedule tasks automatically at a specific time. --- 📌 Examples: * Daily backup at 2 AM 💾 * Clear logs every Sunday 🧹 * Run a script every 5 minutes ⏱️ --- 🧠 Real-life example: Think of an alarm clock ⏰ 👉 You set the time 👉 It automatically reminds or runs Same way, cron runs tasks without manual effort. --- ⚡ Cron format: `* * * * * command` 👉 5 fields mean: Minute | Hour | Day | Month | Day of Week Example: `0 2 * * * backup.sh` (Runs every day at 2 AM) --- 🔍 Useful commands: `crontab -l` → List cron jobs `crontab -e` → Edit cron jobs --- ⚠️ Common mistake: Forgetting to give full path of command/script 👉 Always use full path in cron jobs --- 💡 Final thought: Don’t repeat tasks manually. Automate them using cron and save your time like a pro 🚀 #Linux #LinuxAdmin #DevOps #CloudComputing #Automation #SystemAdministration #LearningInPublic

A bold hook about efficiency or Linux mastery Linux isn't just an OS; it’s a superpower for developers and system admins. I recently came across a breakdown of some essential command-line tips that are too good not to share. The Problem: (e.g., "We often spend too much time doing X manually...") The Solution: (Summarizing the key commands or workflows from the attached PDF). The Benefit: (e.g., "Using these three flags can cut your debugging time in half.") As someone building in the IT space, I’ve found that mastering the CLI is the fastest way to scale operational efficiency. I’ve attached a detailed PDF guide below that dives deeper into these commands. Which Linux command is a "must-have" in your daily workflow? Let’s discuss in the comments! 👇 #Linux #OpenSource #DevOps #SystemAdministration #TechLeadership #Efficiency #TerminalTips #Debian

Rename files in Linux using CLI tools. Methods: • mv → rename single file • rename → batch rename using patterns • loops → bulk rename with mv Examples: • mv file1.txt file2.txt • rename 's/old/new/' *.txt Key points: • mv = move + rename • rename supports regex • useful for automation and bulk operations Full guide 👉 https://lnkd.in/dMiQpmsW #Linux #DevOps #SysAdmin #VSYSHost #CLI #Infrastructure

File permissions in Linux are not just concepts… they directly control who can access, modify, or execute files. Understanding them is essential when working on servers or troubleshooting issues. 🔹 ls -l → Shows file permissions, owner, and group details 🔹 chmod +x script.sh → Gives execute permission to a file 🔹 chmod 755 file → Sets read, write, execute for owner and read/execute for others 🔹 chown user:group file → Changes file ownership 🔹 id → Displays user ID (UID) and group ID (GID) These commands are commonly used when fixing access issues or deploying applications… because one wrong permission can break everything #Linux #LinuxCommands #DevOps #SystemAdmin #CloudComputing

🚨 Real-Time Linux Troubleshooting – Disk Space Full One of the most common production issues in Linux environments is Disk Space Full. When disk space reaches 100%, applications may stop working and system performance can degrade. Here is my troubleshooting approach as a Linux Administrator: 🔎 Step 1: Check Disk Usage Command: "df -h" This command shows the disk usage of all mounted filesystems. 🔎 Step 2: Identify Large Directories Command: "du -sh /*" This helps find which directory is consuming the most disk space. 🔎 Step 3: Drill Down Further Example: "du -sh /var/*" Usually directories like /var/log, /tmp, or application logs consume large space. 🔎 Step 4: Check Large Files Command: "find / -type f -size +500M" This helps locate very large files. 🔎 Step 5: Clean Up Space Possible actions: • Remove old logs • Clear temporary files • Rotate logs • Archive unnecessary files 💡 Key Learning: Regular monitoring of disk usage helps prevent production outages and improves system stability. #Linux #LinuxAdministrator #SysAdmin #LinuxTroubleshooting #DevOps #ITOperationsLinux #LinuxAdministration #DevOps #SystemAdministration #LinuxTips