DEV Community: Munish Kumar sharma

How to Install and Set Up MySQL on Windows 11, Linux, and macOS (2026 Complete Guide)

Munish Kumar sharma — Tue, 03 Mar 2026 06:34:38 +0000

Setting up a database locally is a fundamental backend skill. Whether you're building with Node.js, PHP, Python, or Java — understanding how to install and configure MySQL properly gives you real control over your development environment.

In this 2026 updated guide, you’ll learn:

How to install MySQL on Windows 11
How to install MySQL on Linux (Ubuntu/Debian)
How to install MySQL on macOS
How to secure your installation
How to verify everything works

If you prefer video learning, I’ve also created a full step-by-step walkthrough here:

🎥 Watch the complete installation tutorial:

👉 https://youtu.be/vm5GjZ28MSU

What is MySQL?

MySQL is one of the world’s most popular open-source relational database management systems (RDBMS). It stores data in structured tables and is widely used in modern web development.

It works seamlessly with:

Node.js
PHP
Python
Java
.NET
MERN / MEAN Stack

If you're learning backend development in 2026, MySQL is still highly relevant.

Install MySQL on Windows 11 (2026)

Step 1: Download MySQL Installer

Visit the official MySQL website.
Download MySQL Installer for Windows.
Choose either:

*   Web Installer (small file)

*   Full Installer (offline version)

For most developers, the Web Installer is sufficient.

Step 2: Run the Installer

Open the downloaded file.
Choose setup type:

*   **Developer Default (Recommended)**

*   Server Only

*   Custom

If you're coding, choose Developer Default.

Step 3: Configure MySQL Server

During setup:

Configuration Type → Development Machine
Port → Keep default (3306)
Authentication → Use strong password authentication
Set root password (important)

Complete the configuration process.

Step 4: Verify Installation

Open Command Prompt and run:

mysql --version

If it shows the version number, installation is successful.

You can also open MySQL Workbench to manage databases visually.

Install MySQL on Linux (Ubuntu/Debian)

Step 1: Update System

sudo apt update

Step 2: Install MySQL Server

sudo apt install mysql-server

Step 3: Secure Installation

sudo mysql_secure_installation

Follow the prompts:

Set root password
Remove anonymous users
Disallow remote root login
Remove test database

Choose Yes for most security options.

Step 4: Start and Enable MySQL

sudo systemctl start mysql
sudo systemctl enable mysql

Check status:

sudo systemctl status mysql

sudo mysql -u root -p

Install MySQL on macOS (2026)

Method 1: Using DMG Installer (Recommended)

Download the macOS .dmg installer from the official MySQL website.
Open the file.
Follow installation steps.
Set root password.
MySQL will appear in System Settings.

Method 2: Using Homebrew

If you use Homebrew:

brew update
brew install mysql

Start MySQL:

brew services start mysql

Verify:

mysql --version

Secure Your MySQL Installation

Always run:

mysql_secure_installation

This improves security by:

Removing anonymous users
Disabling remote root login
Removing test databases
Strengthening password setup

Security should never be skipped.

Test Your MySQL Setup

mysql -u root -p

Create a test database:

CREATE DATABASE testdb;
SHOW DATABASES;

If it appears in the list, your installation works perfectly.

Common MySQL Installation Errors (2026)

MySQL Not Recognized as Command

Add MySQL bin folder to your system PATH.

Windows:

Search "Environment Variables"
Add MySQL bin directory to PATH

macOS/Linux:

export PATH="/usr/local/mysql/bin:$PATH"

Port 3306 Already in Use

Edit MySQL configuration file (my.ini or my.cnf) and change the port number.

Why Installing MySQL Locally Still Matters in 2026

Yes, cloud databases like:

AWS RDS
PlanetScale
Supabase

are powerful.

But if you don’t understand:

Local configuration
Services
Authentication
Ports
Security

You’ll struggle when debugging real production systems.

Strong backend developers know their environment inside out.

Final Thoughts

Installing MySQL isn’t just a setup task. It’s foundational backend knowledge.

If you're serious about web development, master these basics before jumping into cloud abstractions.

Again, if you prefer video guidance, watch the complete walkthrough here:

🎥 https://youtu.be/vm5GjZ28MSU

🚀 I Started Learning Java & DSA From Books Instead of Tutorials — Here’s What Happened

Munish Kumar sharma — Sun, 15 Feb 2026 13:43:48 +0000

Building strong Java fundamentals through books, deep thinking, and deliberate practice.

Most developers start Java with YouTube tutorials.

I decided to slow down.

Instead of binge-watching courses at 2x speed, I started learning Java and Data Structures & Algorithms (DSA) primarily through books — and the difference has been powerful.

This is my structured approach and why I believe reading > watching (if you're serious).

📚 The Books I'm Using

I’m currently studying these two books in parallel:

Head First Java by Kathy Sierra & Bert Bates
Java: The Complete Reference by Herbert Schildt

And yes — I’m implementing everything in VS Code as I go.

📘 1️⃣ Head First Java — For Concept Clarity

This book feels different.

It’s not just syntax.
It forces you to think.

What I like about it:

Brain-friendly explanations
Strong focus on OOP fundamentals
Concept-driven learning
Practical mental models

Even though it’s based on older JDK versions, core concepts like:

Classes
Objects
Inheritance
Polymorphism
Encapsulation

…are timeless.

If your fundamentals are strong, version updates don’t scare you.

📕 2️⃣ Java: The Complete Reference — For Depth

This one is more traditional and structured.

It gives:

Detailed explanations
Language internals
API coverage
Advanced concepts
Strong technical precision

If Head First builds intuition, this book builds authority.

Reading them together helps me:

Understand visually
Reinforce technically
Implement practically

🎥 Books vs Tutorials — The Honest Comparison

Let’s be real.

Tutorials & Courses:

✔ Fast

✔ Easy to consume

✔ Great for starting

❌ Passive learning

❌ Easy to binge without retention

❌ Creates illusion of productivity

Books:

✔ Deep understanding

✔ Better retention

✔ Structured knowledge

✔ Builds real problem-solving ability

❌ Slower

❌ Requires focus

❌ No spoon-feeding

🔥 My Conclusion: Reading > Watching (If You’re Serious)

If your goal is:

Cracking top tech companies
Mastering DSA
Thinking like a programmer
Writing clean, structured code
Understanding why something works

Books win.

But here’s the real formula:

📖 Read → 💻 Implement → 🎥 Watch only for doubts → 🔁 Repeat

Courses are tools.
Books are foundation builders.

💻 My Current Learning Plan

Right now I’m focusing on:

Core Java (OOP, memory basics, JVM concepts)
Starting DSA in Java (arrays, recursion, linked lists)
Writing every example manually
No skipping chapters
No rushing

Consistency > Motivation.

🧠 Why I Chose This Path

Most people want shortcuts.

But programming is a craft.

And crafts are built slowly — with depth.

I don’t just want to “know Java.”

I want to understand it properly.

What About You?

Do you prefer learning from books or tutorials?

If you're also learning Java or DSA, let’s connect and grow together 🚀

I Shipped My First VS Code Extension — Here’s What I Learned

Munish Kumar sharma — Sat, 07 Feb 2026 18:18:06 +0000

Every developer has faced this.

You clone a project.
Open it in VS Code.
And then… pause.

“How do I run this?”

You skim the README.
Try one command.
It fails.
Try another.

npm run dev
npm start
flask run
python manage.py runserver
uvicorn main:app --reload

Different projects.
Different frameworks.
Same confusion.

After switching between JavaScript and Python projects for a while, I realized the problem wasn’t skill.

It was friction.

The Hidden Cost of Context Switching

Modern dev work isn’t hard because frameworks are bad.
It’s hard because every framework chooses its own startup ritual.

React (Vite) → npm run dev

Next.js → npm run dev

Angular → npm start

Flask → flask run

Django → python manage.py runserver

FastAPI → uvicorn main:app --reload

If you work across stacks, your brain becomes a lookup table for commands.

That’s wasted mental energy.

Computers are better at pattern detection than humans —
so why are humans doing this work?

The Idea: Let the Editor Handle It

Instead of memorizing commands, I asked:

What if VS Code could detect the project and run it automatically?

That question became my first VS Code extension: WebRun.

The idea is simple:

Open a project

Click ▶️

The correct dev server starts

No configuration.
No cloud services.
No tracking.

Just automation for something developers repeat every day.

How It Works (No AI, No Magic)

WebRun doesn’t guess.
It looks for signals, the same ones developers rely on subconsciously.

package.json

Dependencies and scripts clearly indicate:

Vite

Next.js

CRA

NestJS

Express / Fastify

Framework config files

Files like:

vite.config.js

next.config.js

angular.json

Frameworks announce themselves if you listen.

Python project clues

manage.py → Django

requirements.txt + app.py → Flask

main.py → FastAPI

Folder structure

Common full-stack layouts:

frontend / backend
client / server
web / api

If both are detected, WebRun starts two servers in parallel.

What WebRun Supports

Right now, WebRun supports:

Frontend: React, Next.js, Vue, Angular, Svelte, Astro

Backend (Node): Express, Fastify, NestJS

Backend (Python): Flask, Django, FastAPI

Static HTML/CSS/JS

Full-stack projects

All triggered with one click inside VS Code.

Lessons from Shipping My First Extension

Building was the easy part.
Shipping taught me everything else.

Distribution beats perfection

A perfect tool with zero users doesn’t exist.

Documentation is the product

If people can’t understand it quickly, they uninstall.

Automation > configuration

Every setting you expose is a chance for drop-off.

Open source builds trust fast

Clear scope + MIT license = healthy contributions.

Small tools actually ship

WebRun does one job:

run the project

That focus made shipping possible.

Open Source & Links

WebRun is completely open source and MIT licensed.

VS Code Marketplace:
https://marketplace.visualstudio.com/items?itemName=codewithmishu.webrun

GitHub Repository:
https://github.com/CodeWithMishu/WebRun

Feedback, issues, and contributions are welcome.

Final Thoughts

WebRun isn’t trying to replace the terminal.
It’s trying to remove unnecessary thinking from daily workflows.

If developers repeat something every day,
computers should automate it.

If you’re building developer tools:

Ship early

Learn in public

Iterate based on real usage

That mindset is how WebRun came to life.