Deploying DevOps Portfolio with Git and Vite Issues Resolved

🚀 GitHub for DevOps – Day 4 (Part 2) 🔥 Git Reset Practical — Hands-on Lab Let’s stop theory and actually see what happens 👇 🧪 Step 1: Create Repo mkdir git-reset-lab cd git-reset-lab git init 🧪 Step 2: Create Commits echo "Version 1" > file.txt git add . git commit -m "v1 commit" echo "Version 2" >> file.txt git add . git commit -m "v2 commit" echo "Version 3" >> file.txt git add . git commit -m "v3 commit" 👉 Current state: v1 → v2 → v3 🔥 PART 1: SOFT RESET git reset --soft HEAD~1 ✔ v3 commit removed ✔ Changes still staged 👉 Check: git status 💡 Perfect for fixing commit messages 🔥 PART 2: MIXED RESET git reset HEAD~1 ✔ Commit removed ✔ Changes remain in file ❌ Not staged 👉 You must run: git add . 🔥 PART 3: HARD RESET (⚠️ Dangerous) git reset --hard HEAD~1 ❌ Commit removed ❌ Changes deleted permanently 👉 File goes back to: Version 1 Version 2 🧠 Final Understanding Soft → Keep changes staged Mixed → Keep changes in files Hard → Delete everything 💬 If you cannot control Git history, you cannot survive in real DevOps environments. Follow for more real-world DevOps learning 🚀 #HiteshDevOps #DevOps #Git #GitHub #CI_CD #Docker #Kubernetes #AWS #OpenToWork #HiringDevOps #DevOpsEngineer #TechHiring   #LearningInPublic #BuildInPublic #TechJourney

🚀 𝗦𝗧𝗢𝗣 𝗚𝗢𝗢𝗚𝗟𝗜𝗡𝗚 𝗚𝗜𝗧 𝗖𝗢𝗠𝗠𝗔𝗡𝗗𝗦 𝗘𝗩𝗘𝗥𝗬 𝗧𝗜𝗠𝗘! If you're learning DevOps, Cloud, or Software Development, Git is something you use almost every day. Yet many beginners still keep searching for the same commands again and again. So I created this simple Git Commands CheatSheet to make life easier. 💻 Here are some of the most used Git commands every developer should know: 🔹 "git init" – Create a new repository 🔹 "git add" – Stage your changes 🔹 "git commit" – Save your changes 🔹 "git status" – Check repository status 🔹 "git push" – Upload code to remote repo 🔹 "git pull" – Fetch and merge updates 🔹 "git branch" – Manage branches 🔹 "git merge" – Combine branches Mastering these commands will make your development workflow faster and more efficient. 💡 Pro Tip: The more you practice Git, the more confident you become in real-world projects. 📌 Save this post so you never forget these commands. 💬 Question for developers: Which Git command do you use the most? #Git #DevOps #CloudComputing #SoftwareDevelopment #Programming #TechLearning #Developers

🚀 GitHub for DevOps – Day 4 (Part 1) 🔥 Git Reset — The Most Misunderstood Command in Git As a DevOps Engineer, you’re not just writing code — you’re managing history, fixing mistakes, and maintaining clean repositories. 👉 That’s where git reset becomes powerful. 📌 Simple Meaning: Git reset = Move your project back to a previous commit Example: A → B → C → D Want to go back to B? 👉 git reset B ⚙️ Git Works in 3 Areas (Must Know) 1️⃣ Working Directory → Your files 2️⃣ Staging Area → git add 3️⃣ Repository → commits 🔥 Types of Git Reset 🔹 1. Soft Reset (Safe) 👉 git reset --soft HEAD~1 ✔ Commit removed ✔ Changes still in staging 💡 Use when: You want to fix commit message or recombine commits 🔹 2. Mixed Reset (Default) 👉 git reset HEAD~1 ✔ Commit removed ✔ Staging cleared ✔ Changes still in files 💡 Use when: You added wrong files 🔹 3. Hard Reset (Dangerous ⚠️) 👉 git reset --hard HEAD~1 ❌ Commit removed ❌ Staging removed ❌ Changes deleted permanently 💡 Use when: You want to completely discard changes 📍 When to Use? ✔ Fix wrong commit → soft reset ✔ Remove staged files → mixed reset ✔ Delete everything → hard reset 🚨 Golden Rule 👉 Use git reset only in local branches 👉 Avoid using it on shared/main branches 💬 Real DevOps work is not about tools It’s about controlling changes safely and confidently. #HiteshDevOps  #DevOps #Git #GitHub #CI_CD #Docker #Kubernetes #AWS  #OpenToWork #HiringDevOps #DevOpsEngineer #TechHiring   #LearningInPublic #BuildInPublic #TechJourney

🚀 Why Git & GitHub Commands Are So Important for Developers and DevOps Engineers Recently, I created a Git Command Cheat Sheet to simplify daily development and DevOps tasks. While working on it, I realized how powerful Git and GitHub commands are in modern software development. 🔹 Version Control Git helps track every change made in the codebase. Developers can easily go back to previous versions, compare changes, and maintain a complete history of the project. 🔹 Collaboration With GitHub, multiple developers can work on the same project simultaneously using branches and pull requests, making teamwork more efficient and organized. 🔹 Code Safety & Backup Git ensures that code is safely stored and managed. Even if mistakes happen, commands like git revert, git reset, and git stash help recover work quickly. 🔹 Branching & Experimentation Developers can create separate branches to develop new features or fix bugs without affecting the main codebase. 🔹 CI/CD Integration Git integrates easily with DevOps tools like Jenkins, GitHub Actions, Docker, and Kubernetes, enabling automated build, testing, and deployment pipelines. 🔹 Transparency & Code Review GitHub enables pull requests and code reviews, which improve code quality and help teams maintain clean and reliable code. 💡 Conclusion: Mastering Git commands is essential for developers and DevOps engineers because it improves collaboration, code management, and automation in modern software development workflows. 📌 I recently created a Git Commands Cheat Sheet to make these commands easier to remember and use in daily work. #Git #GitHub #DevOps #AWS #Linux #CloudComputing #CICD #SoftwareDevelopment

🚀 GitHub for DevOps – Day 4 (Part 5) 🔁 Git Revert vs Git Reset – Know the Difference (Very Important in Production) In real-world DevOps environments, handling mistakes safely is more important than just fixing them. Let’s understand two commonly confused commands: git revert and git reset 🔹 1️⃣ Git Revert – Safe Undo (Recommended for Shared Branches) 👉 git revert is used to undo a commit without deleting history 📌 What it does: Creates a new commit Reverses the changes of a specific commit Keeps history clean and traceable 📍 Example: git log --oneline c3 v3 commit b2 v2 commit a1 v1 commit Now revert the latest commit: git revert c3 📍 New log: d4 Revert "v3 commit" c3 v3 commit b2 v2 commit a1 v1 commit ✅ A new commit is created ✅ History is preserved ✅ Safe for production & team environments 🔹 2️⃣ Git Reset – History Rewriting (Use Carefully) 👉 git reset is used to move the branch pointer backward 📌 What it does: Removes commits from history No new commit is created Can rewrite history (dangerous in shared branches) 📍 Example: git reset --hard b2 📍 New log: b2 v2 commit a1 v1 commit ❌ v3 commit is completely removed ❌ No trace of undo action ⚠️ Risky if code is already pushed 🔥 Key Difference ✔️ git revert → Safe, creates a new commit, keeps history ⚠️ git reset → Dangerous, deletes history, no new commit 💡 Pro Tip (MNC Level Practice): Use git revert in production or shared branches Use git reset only for local changes or before pushing 📌 Understanding this difference can save your team from major production issues. #HiteshDevOps #DevOps #Git #GitHub #CI_CD #Docker #Kubernetes #AWS #OpenToWork #HiringDevOps #DevOpsEngineer #TechHiring #LearningInPublic #BuildInPublic #TechJourney

🚀 Master Git: From Basic to Advanced Commands Git is one of the most important tools for every Developer, DevOps Engineer, and Cloud Professional. From tracking code changes to managing team collaboration, Git makes everything smooth. Here’s a quick Git command roadmap from basic to advanced 👇 🔹 Basic Commands 📌 "git init" → Create a new local repository 📌 "git clone <repo-url>" → Copy an existing repository 📌 "git status" → Check current file status 📌 "git add ." → Add all changes to staging 📌 "git commit -m "message"" → Save changes with a message 📌 "git push" → Upload code to remote repository 📌 "git pull" → Fetch and merge latest changes 📌 "git log" → View commit history 🔹 Branching & Collaboration 🌿 "git branch" → List branches 🌿 "git checkout -b feature-branch" → Create and switch branch 🌿 "git merge branch-name" → Merge branch into current branch 🌿 "git rebase main" → Reapply commits on top of another branch 🔹 Advanced Commands ⚡ "git stash" → Temporarily save uncommitted changes ⚡ "git stash pop" → Restore stashed changes ⚡ "git reset --hard HEAD" → Remove local changes ⚡ "git revert <commit-id>" → Undo a specific commit safely ⚡ "git cherry-pick <commit-id>" → Apply selected commit ⚡ "git fetch --all" → Fetch all remote updates ⚡ "git diff" → Compare file changes 💡 Git is not just a skill, it’s the foundation of every CI/CD pipeline. What’s your most-used Git command? 👇 #Git #DevOps #AzureDevOps #Jenkins #Terraform #Docker #Kubernetes #Cloud #LearningJourney #Tech DevOps Insiders

🚀 Stop Merging Everything — Smart Engineers Use git cherry-pick 🍒 | GitHub for DevOps Day 5 (Final Part) In fast-paced DevOps environments, not every change needs a full merge. Sometimes, you only need one specific fix — not the entire branch. That’s where git cherry-pick becomes a powerful tool. 🔹 What is git cherry-pick? git cherry-pick allows you to take a specific commit from one branch and apply it to another branch — without merging everything. 👉 Think of it like picking one cherry 🍒 from a tree, not the whole tree. 🧠 Simple Visualization main: A → B → C feature: D → E 👉 Need only commit D? git cherry-pick <commit-id> ✅ Result: main: A → B → C → D 🧪 Practical Workflow 1️⃣ Check commits git log --oneline 2️⃣ Switch to target branch git checkout main 3️⃣ Apply specific commit git cherry-pick <commit-id> 4️⃣ Verify git log --oneline 🔥 Where is it used? ✔ Bug fixes in production ✔ Hotfixes across multiple branches ✔ Selective feature transfer ✔ Avoiding unnecessary merges ⚡ When should you use it? ✅ You need only one fix, not full feature changes ✅ You want to avoid merge conflicts from unrelated commits ✅ Same fix must be applied to multiple branches (main, staging, etc.) ⚠️ Handling Conflicts If conflicts occur: git add . git cherry-pick --continue 💡 Pro Tip Always verify commit ID before applying: git log --oneline 🔁 Quick Recall ✔ git cherry-pick → copy one commit 🍒 ✔ git fetch → download changes without applying 📥 🚀 Final Takeaway In real-world DevOps workflows, precision matters. 👉 Don’t move entire branches when one commit is enough. #HiteshDevOps #DevOps #Git #GitHub #CI_CD #Docker #Kubernetes #AWS #OpenToWork #HiringDevOps #DevOpsEngineer #TechHiring #LearningInPublic #BuildInPublic #TechJourney

 Expanding My DevOps Toolkit: Mastered Bitbucket Repository Workflows 🚀 Following my recent posts on Git and GitHub, I’ve been diving deeper into Bitbucket to understand its unique role in the DevOps lifecycle. 🛠️ In my latest session, I practiced: ✅ Setting up private repositories with optimized .gitignore and README configurations . ✅ Streamlining local workflows by cloning and managing branches directly from the terminal. ✅ Securely handling authentication through Bitbucket’s App Passwords and authorization settings. ✅ Executing the full add-commit-push cycle to maintain seamless version control. Understanding the nuances between different hosting platforms like Bitbucket and GitHub is key to building flexible, robust CI/CD pipelines. Looking forward to applying these skills to more complex deployment scenarios! ➡️Bitbucket Repository Management Summary The tutorial provides a step-by-step walkthrough of the following DevOps tasks: Repository Creation: Initiating a new private repository named "myrepo" within a workspace, including configurations for a README file and .gitignore template. Local Cloning: Using the git clone command in a terminal to sync the cloud repository with a local machine. Branching & File Management: Creating a new "master" branch and using the touch command to generate new files (e.g., "amazon", "microsoft", and "google"). Committing & Pushing Changes: Staging files with git add, committing them with descriptive messages, and pushing the updates back to Bitbucket using git push origin master. Security Settings: Navigating the Bitbucket interface to manage app authorizations and app passwords, which are essential for secure API and command-line interactions. #DevOps #Bitbucket #VersionControl #ContinuousIntegration #Git #TechLearning Frontlines EduTech (FLM)

🚀 Day 11/30 – Git Installation & Essential Git Commands Continuing my AWS + DevOps learning journey with Fortune Cloud Technologies Private Limited, today I explored Git installation, configuration, and essential Git commands used in real development workflows. Git is one of the most important tools for version control and collaboration in modern software development. Here are some key things I practiced today: 🔹 Installing Git (Ubuntu/Debian). 🔹 Configuring username and email for commits. 🔹 Verifying Git configuration. I also revised some commonly used Git commands such as: ✔ git init – Initialize a repository ✔ git clone – Clone a remote repository ✔ git status – Check repository status ✔ git add – Stage changes ✔ git commit – Save changes to repository ✔ git push – Upload changes to remote repository ✔ git pull – Fetch and merge remote changes ✔ git branch & git checkout – Branch management ✔ git merge & git rebase – Combine branches ✔ git stash – Save uncommitted changes. Understanding these commands is essential for efficient collaboration, code management, and CI/CD pipelines in DevOps environments. 💡 Consistent practice with Git makes managing code changes much easier. 💬 What Git command do you use most frequently? #Git #DevOps #VersionControl #AWS #ContinuousLearning #FortuneCloudTechnologiesPrivateLimited

𝑰 𝑱𝒖𝒔𝒕 𝑩𝒖𝒊𝒍𝒕 𝑺𝒐𝒎𝒆𝒕𝒉𝒊𝒏𝒈 𝑰 𝑾𝒊𝒔𝒉 𝑰 𝑯𝒂𝒅 5 𝒀𝒆𝒂𝒓𝒔 𝑨𝒈𝒐 Starting today, I am sharing 20𝑫𝒂𝒚𝒔𝑶𝒇𝑫𝒐𝒄𝒌𝒆𝒓, a completely free Docker learning challenge on GitHub. Why? Learning Docker was confusing for me: 🎥 Long YouTube videos that wasted time 📚 Articles jumping around with no clear path 💸 Expensive courses that became outdated ❌ Nobody explained why things matter, just how So I created something different. What’s Inside: 𝐖𝐞𝐞𝐤 1 (𝐃𝐚𝐲𝐬 1-7): 𝐁𝐚𝐬𝐢𝐜𝐬 What is Docker & how do images work Write your first Dockerfile Run & manage containers Connect containers Save data with Volumes Use Docker Compose 𝐖𝐞𝐞𝐤 2 (𝐃𝐚𝐲𝐬 8-14): 𝐆𝐞𝐭 𝐛𝐞𝐭𝐭𝐞𝐫 Advanced Compose Make images smaller & faster Best practices & debugging Security tips (Day 14 is detailed!) 𝐖𝐞𝐞𝐤 3 (𝐃𝐚𝐲𝐬 15-20): 𝐆𝐨 𝐩𝐫𝐨𝐟𝐞𝐬𝐬𝐢𝐨𝐧𝐚𝐥 Monitor containers Connect Docker to CI/CD Orchestration & microservices Deploy to production Build a real project 𝐖𝐡𝐲 𝐈𝐭’𝐬 𝐃𝐢𝐟𝐟𝐞𝐫𝐞𝐧𝐭: ✅ Real examples & copy-paste code ✅ Clear, simple explanations ✅ Hands-on exercises with solutions ✅ Organized day by day ✅ Completely free & always updated 𝐖𝐡𝐲 𝐘𝐨𝐮 𝐒𝐡𝐨𝐮𝐥𝐝 𝐂𝐚𝐫𝐞: 🏢 80% of tech companies use Docker 💼 DevOps jobs almost always require it 💰 Docker skills can boost salary 15-25% 📈 Essential for modern apps & microservices 𝐇𝐨𝐰 𝐈𝐭 𝐖𝐨𝐫𝐤𝐬: Each day: folder + objectives + exercises + solutions Time: 30 min – 2 hours per day 𝓝𝓮𝔁𝓽 𝓢𝓽𝓮𝓹𝓼: ⭐ 𝑺𝒕𝒂𝒓 𝒕𝒉𝒆 𝒓𝒆𝒑𝒐 𝒐𝒏 𝑮𝒊𝒕𝑯𝒖𝒃 📖 𝑹𝒆𝒂𝒅 𝑫𝒂𝒚 1 - 𝑫𝒐𝒄𝒌𝒆𝒓 𝑩𝒂𝒔𝒊𝒄𝒔 💻 𝑫𝒐 𝒆𝒙𝒆𝒓𝒄𝒊𝒔𝒆𝒔 & ✅ 𝒄𝒉𝒆𝒄𝒌 𝒔𝒐𝒍𝒖𝒕𝒊𝒐𝒏𝒔 📤 𝑺𝒉𝒂𝒓𝒆 𝒑𝒓𝒐𝒈𝒓𝒆𝒔𝒔 𝑾𝒉𝒐 𝑰𝒔 𝑻𝒉𝒊𝒔 𝑭𝒐𝒓? 𝑩𝒆𝒈𝒊𝒏𝒏𝒆𝒓𝒔, 𝒃𝒂𝒄𝒌𝒆𝒏𝒅 𝒅𝒆𝒗𝒆𝒍𝒐𝒑𝒆𝒓𝒔, 𝒄𝒂𝒓𝒆𝒆𝒓 𝒄𝒉𝒂𝒏𝒈𝒆𝒓𝒔 𝑨𝒏𝒚𝒐𝒏𝒆 𝒘𝒂𝒏𝒕𝒊𝒏𝒈 𝒃𝒆𝒕𝒕𝒆𝒓-𝒑𝒂𝒚𝒊𝒏𝒈 𝒋𝒐𝒃𝒔 𝑷𝒆𝒐𝒑𝒍𝒆 𝒘𝒉𝒐 𝒕𝒓𝒊𝒆𝒅 𝑫𝒐𝒄𝒌𝒆𝒓 𝒃𝒖𝒕 𝒈𝒐𝒕 𝒍𝒐𝒔𝒕 𝐃𝐚𝐲 1 𝐢𝐬 𝐥𝐢𝐯𝐞 𝐓𝐎𝐃𝐀𝐘. 𝐓𝐨𝐦𝐨𝐫𝐫𝐨𝐰, 𝐃𝐚𝐲 2 𝐝𝐫𝐨𝐩𝐬, 𝐚𝐧𝐝 𝐢𝐭 𝐜𝐨𝐧𝐭𝐢𝐧𝐮𝐞𝐬 𝐟𝐨𝐫 20 𝐝𝐚𝐲𝐬. 🐳 𝐋𝐞𝐚𝐫𝐧 𝐃𝐨𝐜𝐤𝐞𝐫 𝐩𝐫𝐨𝐩𝐞𝐫𝐥𝐲. 𝐁𝐮𝐢𝐥𝐝 𝐫𝐞𝐚𝐥 𝐬𝐤𝐢𝐥𝐥𝐬. 𝐁𝐨𝐨𝐬𝐭 𝐲𝐨𝐮𝐫 𝐜𝐚𝐫𝐞𝐞𝐫. GitHub https://lnkd.in/dtVn3ieP #Docker #DevOps #FreeLearning #OpenSource #CareerGrowth #Tech