𝟭.𝗴𝗶𝘁 𝗱𝗶𝗳𝗳: Show file differences not yet staged.
𝟮. 𝗴𝗶𝘁 𝗰𝗼𝗺𝗺𝗶𝘁 -m "commit message": Commit all tracked changes with a message.
𝟯. 𝗴𝗶𝘁 𝘀𝘁𝗮𝘁𝘂𝘀: Show the state of your working directory.
𝟰. 𝗴𝗶𝘁 𝗮𝗱𝗱 𝗳𝗶𝗹𝗲_𝗽𝗮𝘁𝗵: Add file(s) to the staging area.
𝟱. 𝗴𝗶𝘁 𝗰𝗵𝗲𝗰𝗸𝗼𝘂𝘁 -𝗯 𝗯𝗿𝗮𝗻𝗰𝗵_𝗻𝗮𝗺𝗲: Create and switch to a new branch.
𝟲. 𝗴𝗶𝘁 𝗰𝗵𝗲𝗰𝗸𝗼𝘂𝘁 𝗯𝗿𝗮𝗻𝗰𝗵_𝗻𝗮𝗺𝗲: Switch to an existing branch.
𝟳. 𝗴𝗶𝘁 𝗰𝗼𝗺𝗺𝗶𝘁 --𝗮𝗺𝗲𝗻𝗱: Modify the last commit.
𝟴. 𝗴𝗶𝘁 𝗽𝘂𝘀𝗵 𝗼𝗿𝗶𝗴𝗶𝗻 𝗯𝗿𝗮𝗻𝗰𝗵_𝗻𝗮𝗺𝗲: Push a branch to a remote.
𝟵. 𝗴𝗶𝘁 𝗽𝘂𝗹𝗹: Fetch and merge remote changes.
𝟭𝟬. 𝗴𝗶𝘁 𝗿𝗲𝗯𝗮𝘀𝗲 -𝗶: Rebase interactively, rewrite commit history.
𝟭𝟭. 𝗴𝗶𝘁 𝗰𝗹𝗼𝗻𝗲: Create a local copy of a remote repo.
𝟭𝟮. 𝗴𝗶𝘁 𝗺𝗲𝗿𝗴𝗲: Merge branches together.
𝟭𝟯. 𝗴𝗶𝘁 𝗹𝗼𝗴-𝘀𝘁𝗮𝘁: Show commit logs with stats.
𝟭𝟰. 𝗴𝗶𝘁 𝘀𝘁𝗮𝘀𝗵: Stash changes for later.
𝟭𝟱. 𝗴𝗶𝘁 𝘀𝘁𝗮𝘀𝗵 𝗽𝗼𝗽: Apply and remove stashed changes.
𝟭𝟲. 𝗴𝗶𝘁 𝘀𝗵𝗼𝘄 𝗰𝗼𝗺𝗺𝗶𝘁_𝗶𝗱: Show details about a commit.
𝟭𝟳. 𝗴𝗶𝘁 𝗿𝗲𝘀𝗲𝘁 𝗛𝗘𝗔𝗗~𝟭: Undo the last commit, preserving changes locally.
𝟭𝟴. 𝗴𝗶𝘁 𝗳𝗼𝗿𝗺𝗮𝘁-𝗽𝗮𝘁𝗰𝗵-𝟭 𝗰𝗼𝗺𝗺𝗶𝘁_𝗶𝗱: Create a patch file for a specific commit.
𝟭𝟵. 𝗴𝗶𝘁 𝗮𝗽𝗽𝗹𝘆 𝗽𝗮𝘁𝗰𝗵_𝗳𝗶𝗹𝗲_𝗻𝗮𝗺𝗲: Apply changes from a patch file.
𝟮𝟬. 𝗴𝗶𝘁 𝗯𝗿𝗮𝗻𝗰𝗵 -𝗗 𝗯𝗿𝗮𝗻𝗰𝗵_𝗻𝗮𝗺𝗲: Delete a branch forcefully.
𝟮𝟭. 𝗴𝗶𝘁 𝗿𝗲𝘀𝗲𝘁: Undo commits by moving branch reference.
𝟮𝟮. 𝗴𝗶𝘁 𝗿𝗲𝘃𝗲𝗿𝘁: Undo commits by creating a new commit.
𝟮𝟯. 𝗴𝗶𝘁 𝗰𝗵𝗲𝗿𝗿𝘆-𝗽𝗶𝗰𝗸 𝗰𝗼𝗺𝗺𝗶𝘁_𝗶𝗱: Apply changes from a specific commit.
𝟮𝟰. 𝗴𝗶𝘁 𝗯𝗿𝗮𝗻𝗰𝗵: Lists branches.
𝟮𝟱. 𝗴𝗶𝘁 𝗿𝗲𝘀𝗲𝘁 --𝗵𝗮𝗿𝗱: Resets everything to a previous commit, erasing all uncommitted changes.
Please open Telegram to view this post
VIEW IN TELEGRAM
We curated a dedicated website showcasing real-time DevOps and Cloud projects — from beginner-friendly setups to advanced, production-grade pipelines. Whether you're just starting out or want to level up your DevOps skills, this site has hands-on projects that cover:
Perfect for self-learning, building your portfolio, and prepping for DevOps interviews — every project is clearly explained with architecture diagrams, tools used, and objectives.
Whether you're just starting out or looking to level up your DevOps journey, this is your one-stop hub for practical experience!
Please open Telegram to view this post
VIEW IN TELEGRAM
Telegram
The DevOps Classroom
🚀 Learn DevOps step by step!
CI/CD, Docker, Kubernetes, Git, Linux, Cloud & more.
Bite-sized tips, tools, and tutorials for beginners & aspiring DevOps engineers.
Join the journey to modern infrastructure!
CI/CD, Docker, Kubernetes, Git, Linux, Cloud & more.
Bite-sized tips, tools, and tutorials for beginners & aspiring DevOps engineers.
Join the journey to modern infrastructure!
Ready to dive into the world of DevOps but overwhelmed by where to start?
Whether you're a beginner or transitioning into a DevOps role, this is the channel you’ve been looking for.
Most DevOps channels are either:
@DevOpsClassroom is built like a course — but FREE, community-driven, and always growing.
You're not just scrolling — you're actually learning.
Please open Telegram to view this post
VIEW IN TELEGRAM
You're using Linux 🐧 wrong!
Most people dive into Linux without truly understanding its file system hierarchy, leading to confusion and inefficiency.
Ever wondered why system files are scattered across /bin, /sbin, and /usr/bin? Or why logs are in /var/log instead of /log?
Here’s a breakdown of the Linux File System Hierarchy to clear up the confusion:
╰ / - Root directory (everything starts here)
╰ /bin - Essential binaries (ls, cp, mv)
╰ /boot - Boot loader files (kernel, GRUB)
╰ /dev - Device files (USB, HDD, tty)
╰ /etc - Configuration files
╰ /home - User home directories
╰ /lib - Essential system libraries
╰ /media - Auto-mounted media (USB, CD)
╰ /mnt - Temporary mount point
╰ /opt - Third-party software packages
╰ /proc - Virtual filesystem for processes
╰ /root - Root user’s home directory
╰ /run - Runtime process data
╰ /sbin - System binaries (fsck, reboot)
╰ /srv - Server-specific data
╰ /sys - Kernel system information
╰ /tmp - Temporary files (cleared on reboot)
╰ /usr - User applications and tools
╰ /usr/bin - Non-essential user binaries
╰ /usr/lib - Libraries for /usr/bin
╰ /usr/local - Locally installed software
╰ /usr/share - Shared data (icons, docs)
╰ /var - Variable data (logs, cache, mail)
╰ /var/log - System logs
╰ /var/spool - Queued jobs (print, mail)
Understanding this structure helps you -
🔠 Locate files efficiently
🔠 Troubleshoot system issues faster
🔠 Optimize performance & security
📱 𝐅𝐨𝐥𝐥𝐨𝐰 @prodevopsguy 𝐟𝐨𝐫 𝐦𝐨𝐫𝐞 𝐬𝐮𝐜𝐡 𝐜𝐨𝐧𝐭𝐞𝐧𝐭 𝐚𝐫𝐨𝐮𝐧𝐝 𝐜𝐥𝐨𝐮𝐝 & 𝐃𝐞𝐯𝐎𝐩𝐬!!! // 𝐉𝐨𝐢𝐧 𝐟𝐨𝐫 𝐃𝐞𝐯𝐎𝐩𝐬 𝐃𝐎𝐂𝐬: @devopsdocs
Most people dive into Linux without truly understanding its file system hierarchy, leading to confusion and inefficiency.
Ever wondered why system files are scattered across /bin, /sbin, and /usr/bin? Or why logs are in /var/log instead of /log?
Here’s a breakdown of the Linux File System Hierarchy to clear up the confusion:
╰ / - Root directory (everything starts here)
╰ /bin - Essential binaries (ls, cp, mv)
╰ /boot - Boot loader files (kernel, GRUB)
╰ /dev - Device files (USB, HDD, tty)
╰ /etc - Configuration files
╰ /home - User home directories
╰ /lib - Essential system libraries
╰ /media - Auto-mounted media (USB, CD)
╰ /mnt - Temporary mount point
╰ /opt - Third-party software packages
╰ /proc - Virtual filesystem for processes
╰ /root - Root user’s home directory
╰ /run - Runtime process data
╰ /sbin - System binaries (fsck, reboot)
╰ /srv - Server-specific data
╰ /sys - Kernel system information
╰ /tmp - Temporary files (cleared on reboot)
╰ /usr - User applications and tools
╰ /usr/bin - Non-essential user binaries
╰ /usr/lib - Libraries for /usr/bin
╰ /usr/local - Locally installed software
╰ /usr/share - Shared data (icons, docs)
╰ /var - Variable data (logs, cache, mail)
╰ /var/log - System logs
╰ /var/spool - Queued jobs (print, mail)
Understanding this structure helps you -
Please open Telegram to view this post
VIEW IN TELEGRAM
Many DevOps Engineers struggle to fully understand the structure of an Ansible directory and how everything ties together.
To make it easier, I've broken it down to help you better understand each component and its purpose.
Please open Telegram to view this post
VIEW IN TELEGRAM
DevOps & Cloud (AWS, AZURE, GCP) Tech Free Learning
Check it out now and level up your DevOps skills!
#DevOps #CheatSheet #InfrastructureManagement #Ansible #Chef #Puppet #Terraform
Please open Telegram to view this post
VIEW IN TELEGRAM
Please open Telegram to view this post
VIEW IN TELEGRAM
(Specific role simulation part of KodeKloud)
(Many rooms cover Linux, Docker, K8s security from an offensive/defensive perspective)
(Similar to TryHackMe, CTFs often involve DevOps tool exploitation/hardening)
(Classic command-line challenges, starting with Bandit for Linux basics)
(Collection of simple games explaining cloud-native concepts)
Please open Telegram to view this post
VIEW IN TELEGRAM
Please open Telegram to view this post
VIEW IN TELEGRAM
Forwarded from The DevOps Classroom
Just deployed a full-stack 3-tier application on AWS EKS with a real-world infrastructure setup!
Key AWS Components:
Check it out & give it a
#DevOps #AWS #EKS #Kubernetes #CICD #FullStack #CloudNative #React #Flask #Postgres
Please open Telegram to view this post
VIEW IN TELEGRAM
DevOps & Cloud (AWS, AZURE, GCP) Tech Free Learning
Photo
𝟭. 𝗖𝗿𝗲𝗮𝘁𝗲 𝗮 𝗦𝗶𝗺𝗽𝗹𝗲 𝗪𝗲𝗯𝘀𝗶𝘁𝗲 𝗨𝘀𝗶𝗻𝗴 𝘁𝗵𝗲 𝗖𝗹𝗼𝘂𝗱
𝗦𝗸𝗶𝗹𝗹𝘀: Terraform, cloud setup, Git.
1. Use 𝗧𝗲𝗿𝗿𝗮𝗳𝗼𝗿𝗺 to create a cloud computer (e.g., AWS EC2 instance).
2. Install a web server (like Apache) and host a basic webpage.
3. Document everything and share it on GitHub.
𝗛𝗲𝗹𝗽𝗳𝘂𝗹 𝗟𝗶𝗻𝗸𝘀:
- Terraform Documentation
- AWS EC2 Quick Start
𝟮. 𝗕𝘂𝗶𝗹𝗱 𝗮 𝗡𝗲𝘁𝘄𝗼𝗿𝗸 𝗠𝗼𝗻𝗶𝘁𝗼𝗿𝗶𝗻𝗴 𝗧𝗼𝗼𝗹
𝗦𝗸𝗶𝗹𝗹𝘀: Python, Bash, networking basics.
1. Write a Python script to check if websites are working.
2. Add extra features like connection speed checks.
3. Show results using a tool like 𝗚𝗿𝗮𝗳𝗮𝗻𝗮.
𝗛𝗲𝗹𝗽𝗳𝘂𝗹 𝗟𝗶𝗻𝗸𝘀:
- Python Networking Guide
- Grafana Setup Guide
𝟯. 𝗔𝘂𝘁𝗼𝗺𝗮𝘁𝗲 𝗖𝗼𝗱𝗲 𝗧𝗲𝘀𝘁𝗶𝗻𝗴 𝘄𝗶𝘁𝗵 𝗖𝗜/𝗖𝗗
𝗦𝗸𝗶𝗹𝗹𝘀: Git, Docker, AWS CodePipeline.
1. Create a small app in Python or another language.
2. Package the app using 𝗗𝗼𝗰𝗸𝗲𝗿.
3. Set up a cloud-based CI/CD pipeline for automated testing.
𝗛𝗲𝗹𝗽𝗳𝘂𝗹 𝗟𝗶𝗻𝗸𝘀:
- Git Basics
- Docker Documentation
- AWS CodePipeline Guide
𝟰. 𝗔𝘂𝘁𝗼𝗺𝗮𝘁𝗲 𝗖𝗹𝗼𝘂𝗱 𝗖𝗹𝗲𝗮𝗻𝘂𝗽
𝗦𝗸𝗶𝗹𝗹𝘀: Bash, Python, cloud cost management.
1. Write a script to find unused cloud resources like idle servers.
2. Automate the script to run daily.
3. Generate a report showing savings.
𝗛𝗲𝗹𝗽𝗳𝘂𝗹 𝗟𝗶𝗻𝗸𝘀:
- AWS Boto3 for Python
- Azure CLI Documentation
𝟱. 𝗦𝗲𝘁 𝗨𝗽 𝗮 𝗖𝗹𝗼𝘂𝗱 𝗕𝗮𝗰𝗸𝘂𝗽 𝗦𝘆𝘀𝘁𝗲𝗺
𝗦𝗸𝗶𝗹𝗹𝘀: Bash, PowerShell, cloud storage.
1. Write a script to copy files from your computer to cloud storage (e.g., AWS S3).
2. Enable versioning to keep multiple file copies.
3. Test by recovering a file.
𝗛𝗲𝗹𝗽𝗳𝘂𝗹 𝗟𝗶𝗻𝗸𝘀:
- AWS S3 Documentation
- Azure Blob Storage Guide
Please open Telegram to view this post
VIEW IN TELEGRAM