Forem: Vansh Tyagi

Understanding the Git Staging Area — One Step You Shouldn’t Skip

Vansh Tyagi — Fri, 16 May 2025 10:24:09 +0000

If you’re new to Git, you might’ve seen this flow:
git add . git commit -m "message"
But have you ever wondered what happens between add and commit? That middle ground is called the staging area — and it's more powerful than you think.

What is the Staging Area?
The staging area (also known as the index) is like a buffer zone. It’s where Git holds your changes temporarily before you officially commit them.
Think of it like a “draft” section in your email you prepare your message, double-check it, and only then hit send.

** Why is it Important?**

Control
You can choose exactly which files to commit. Modify 10 files but only want to commit 2? Staging makes that easy.
Safe Checkpoint
It lets you pause, review, and revise what’s going in your next commit.
Clean Commit History
Break your changes into logical commits, instead of dumping everything in one big commit.

Key Commands to Know

What You Want to Do	Git Command
Add a specific file	`git add filename`
Add all modified files	`git add .`
Check what’s staged	`git status`
Unstage a file	`git restore --staged filename`
Commit staged files	`git commit -m "message"`

What If You Don’t Use the Staging Area?

Skipping the staging step isn’t “wrong,” but you lose control. You might:
• Commit files you didn’t mean to
• Push code that’s half-baked
• End up with messy history that’s hard to read (or debug!)

Quick Recap

• Staging area = Preparation zone
• Gives you control, clarity, and clean commits
• Learn it early, and your future self (and team) will thank you.

Author’s Note:
If you’re still confused between git add and git commit, you’re not alone, I was too! Drop your doubts or favorite Git tips in the comments. Let’s grow together.

Why Every DevOps Engineer Should Know About /etc/hosts

Vansh Tyagi — Thu, 15 May 2025 11:20:24 +0000

Introduction
If you are new to Linux or DevOps, you might think DNS (domain name system) is something only big servers or cloud services handle. But there is a simple file on your computer that helps your system know which IP address matches a website name or server name.
That file is called /etc/hosts. It’s small but very important!

What is /etc/hosts?
/etc/hosts is a text file on your computer that connects names to IP addresses.
For example:
127.0.0.1 localhost 192.168.1.10 myserver.local

This means your computer knows:
• localhost is your own computer (IP 127.0.0.1)
• myserver.local is at IP address 192.168.1.10

Why Should You Care?
Here are some easy reasons why /etc/hosts is useful for beginners learning DevOps:

Test websites or services locally You can pretend that a website or server is at a specific address on your own computer.

Example: 127.0.0.1 mytestsite.local
Now if you open a browser and go to mytestsite.local, your computer looks for it on your own machine.

Fix name problems quickly
If your internet’s DNS server has issues, your system won’t find websites by name. Using /etc/hosts, you can tell your computer where to find important servers without relying on the internet.
Redirect websites for testing
Say you want to see how your app works if it connects to a different server. You can change /etc/hosts to make the name point somewhere else, like a test server.

How to Edit /etc/hosts?
• You need admin rights (use sudo on Linux)
• Open the file with a text editor, for example:

sudo nano /etc/hosts

• Add or change lines like:
127.0.0.1 mylocalapp.local

• Save and exit the editor.

Important Tips

• This file only works on your computer — it won’t affect other machines.
• Be careful while editing; a wrong entry can cause connection problems.
• Always backup before making big changes:

sudo cp /etc/hosts /etc/hosts.backup

Conclusion
Even though it’s simple, /etc/hosts is one of the most powerful tools in your DevOps toolbox. It helps you understand how computers find each other on a network — a very important concept for anyone working with servers, cloud, or containers.

Can’t Login as Root on Ubuntu? Here’s the Real Reason and How to Fix It.

Vansh Tyagi — Tue, 13 May 2025 12:19:58 +0000

Introduction
If you’ve worked with CentOS or other RHEL-based systems, you're probably used to logging in directly as root no extra setup needed. But when you switch to Ubuntu, things are different. You try to login as root and get blocked. Even sudo su - might throw permission errors if you're not careful.
So what's going on here? Is it a bug? A restriction? No — it’s a security feature. Ubuntu disables direct root login by default to prevent unauthorized or accidental system damage. But if you're setting up a lab environment, testing on local, or just want full control here’s how you can enable root login on Ubuntu (safely and responsibly).

Steps to Enable Root Login in Ubuntu
Use this only in testing, learning, or non-production environments.

Step 1: Allow Root Login via SSH.
Open the SSH configuration file using a text editor.
sudo vi /etc/ssh/sshd_config
Find this line: PermitRootLogin prohibit-password
Change it to: PermitRootLogin yes
This line tells SSH that root login is now allowed using a password.

Step 2: Restart the SSH Service.
sudo systemctl restart ssh

Step 3: Set Root Password.
sudo passwd root

Step 4: Switch to Root User
su -
Here, You'll be prompted to enter the root password you set earlier.
Boom — you're now logged in as root.

Important
• Never enable root login on a public-facing production server.
• Use strong passwords if enabling this temporarily.
• Consider reverting the changes once you're done with your learning/test session.

Conclusion
Ubuntu disables root login by default not because it lacks the capability, but as a deliberate security measure. Once you understand this philosophy, you can confidently enable root access when needed and use it wisely.

Hidden Gem for Linux Learners: Install Linux on Windows with wsl --install (No VM, No Cloud, No Cost!)

Vansh Tyagi — Mon, 12 May 2025 11:59:03 +0000

Introduction:
Many beginners believe that to learn Linux, they must rent an EC2 instance on AWS or create a virtual machine on Azure or GCP. These cloud options work, but let’s be real they come with a price tag and internet dependency. But what if I told you there’s a pocket-friendly, offline, and genuine way to run Linux directly on your Windows system?
Yes, it's called WSL (Windows Subsystem for Linux) and in most cases, a single command gets the job done:
wsl --install

But wait... it’s not always that simple. Let’s walk through the full, real-world guide including the common error traps and how to fix them.

What is WSL?
WSL allows you to run a real Linux environment natively on Windows, without dual-booting or installing a separate virtual machine. It supports tools like Bash, Git, apt, and even Docker right from your Windows machine.

Prerequisites Before You Run wsl --install
Here’s where most people trip up (yes, me too!). Even though Microsoft says “just run the command,” WSL depends on your system’s BIOS and hardware settings. Make sure to:
Enable Virtualization in BIOS
Step 1: Reboot your system.
Step 2: Enter in your BIOS/UEFI (usually by pressing F2, Del, or Esc)
Step 3: Navigate to the Configuration Tab.
Step 4: Select Virtualization.
Step 5: Press Enter, and change the status "Enabled"
Step 6: Navigate to Save & Exit

What after enabling Virtualization in BIOS ?
Step 1: Go to your computer's Command Prompt (CMD)
Step 2: Execute wsl --install command.
Step 3: Give username of your Linux environment.
Step 4: Provide password to your Linux user.

Why This is a Hidden Gem (And Cost-Saver!)
• No cloud fees.
• No internet dependency after setup.
• No need for heavy VMs like VirtualBox or VMware.
• Fully functional Linux terminal inside Windows.
• Works great even on mid-range laptops.

Conclusion:
In a world where people are renting servers and spinning up costly VMs to “learn Linux,” WSL stands out as a free, fast, and frictionless alternative. Just configure your BIOS, run wsl --install, and you're good to go. Trust me — if you're learning Linux, this is the most underrated tool on your machine.

Author’s Note:
Tried this out? Got stuck? Let me know in the comments or connect with me — I’ve been through the errors and figured out the tweaks.