I Put Linux in the Browser So You Don't Have to Install a VM

Fyodor Dostoevsky — Sun, 19 Jul 2026 10:17:25 +0000

Hello everyone! I'm Asim Ayaz

I'm a DevOps & InfoSec student and open-source contributor. I run Fedora as my daily driver, and I love building free tools that lower the barrier to entry for people learning tech.

Today I want to share Web Linux a project I built because I was tired of telling my friends to "just install a VM" to practice Linux commands.

The Problem

Every time someone asks me "how do I learn Linux?" I give them the same answer:

Download VirtualBox
Download an ISO
Allocate 4GB of RAM
Fight with display drivers for 3 hours
Finally open a terminal

By step 3, they've already given up.

I thought: "What if you could practice Linux commands directly in your browser? No install. No VM. Just a URL."

The Solution: Web Linux

Web Linux is a browser-based Linux environment that lets you:

✅ Run common Linux commands in a terminal-like interface
✅ Practice file system navigation (ls, cd, pwd, mkdir)
✅ Learn command syntax without breaking your own system
✅ Access it from any device — phone, tablet, Chromebook
✅ Zero setup, zero install, zero risk

Live Demo: web-linux-delta.vercel.app

Why This Matters

When I started learning Linux a year ago, I was terrified of typing the wrong command and bricking my system. Having a sandbox in the browser would've saved me weeks of anxiety.

Web Linux isn't a full VM, it's a safe, educational layer that behaves like a real terminal. Perfect for:

Students preparing for Linux certifications (LPIC, RHCSA, CompTIA Linux+)
Windows/Mac users curious about the command line
Beginners who want to practice rm -rf without consequences 😄

The Tech Stack

Layer	Tech	Why
Frontend	HTML + CSS + Vanilla JS	Fast, no framework bloat
Terminal UI	Custom-built or Xterm.js	Familiar CLI feel in the browser
Logic	Client-side JavaScript	Instant feedback, no server latency
Hosting	Vercel	Free, fast, global edge network

A Real Example

Type this in Web Linux:

$ ls -la
$ mkdir projects
$ cd projects
$ touch hello.txt
$ echo "Hello from Web Linux" &gt; hello.txt
$ cat hello.txt

What I Learned

The browser is more powerful than we think You don't always need a backend. Parsing commands, maintaining a virtual file system, and rendering output can all happen client-side.
UX matters for beginners Real terminals are intimidating. A blinking cursor with no context is scary. I added: Command hints and autocomplete suggestions Color-coded output (errors in red, success in green) A "cheat sheet" sidebar for common commands
Teaching is the best way to learn Building this forced me to truly understand how Linux file systems work. I had to model cd, pwd, and relative paths in JavaScript. Now I know them cold. What's Next [ ] Pipe support (cat file.txt | grep "error") [ ] More commands (chmod, chown, ps, top) [ ] Interactive tutorials (e.g., "Learn grep in 5 minutes") [ ] Dark mode toggle (because obviously) Star the repo to follow along — I push updates every weekend. Try It / Contribute 🔗 Live App: web-linux-delta.vercel.app ⭐ GitHub Repo: github.com/YOUR_USERNAME/web-linux 🐛 Found a bug or want a new command? Open an issue — I read every single one. Did you learn Linux in a VM, WSL, or straight on bare metal? What's your advice for absolute beginners? Drop a comment below 👇 plain

I Built a Lightweight Postman Alternative Because My Laptop Was Dying

Fyodor Dostoevsky — Sun, 19 Jul 2026 08:30:02 +0000

The Problem

I was learning DevOps and APIs this summer. Every time I wanted to test a quick endpoint, I had two options:

Open Postman — which takes 5 seconds to load, eats 800MB of RAM, and updates every 3 days
Use curl — which is great until you need to format JSON, add headers, or see a pretty response

My laptop (running Fedora, 8GB RAM) would start fanning like a jet engine. For a simple GET request.

I thought: "Why does API testing need to be a desktop app?"

The Solution: API-Sisyphus

I built a web-based API client that:

✅ Loads instantly in your browser
✅ Zero install (just a URL)
✅ Sends GET, POST, PUT, DELETE with custom headers
✅ Pretty-prints JSON responses
✅ Runs on Vercel's free tier

Live Demo: api-sisyphus.vercel.app

Why "Sisyphus"?

> "One must imagine Sisyphus happy." — Albert Camus

Because debugging APIs is pushing a boulder up a hill. You fix one 500 error, another appears. The struggle itself is enough to fill a developer's heart.

Also, the domain was available.

How It Works

The UI is dead simple:

Paste your API URL
Pick the HTTP method
Add headers/body if needed
Hit SEND
See formatted response + status code + latency

No tabs. No workspaces. No "syncing to cloud." Just you and the endpoint.

The Tech Stack

Layer	Tech	Why
Frontend	Vanilla JS + HTML	No build step, instant load
Styling	CSS custom properties	Dark mode ready
Hosting	Vercel	Free, global CDN, auto-deploy from Git
Backend	None	Pure client-side fetch() — your data never touches my server

A Real Example

Testing a public API:


javascript
// What the tool sends behind the scenes
fetch('https://api.github.com/users/abyss', {
  method: 'GET',
  headers: {
    'Accept': 'application/vnd.github.v3+json'
  }
})
Response:
JSON
{
  "login": "abyss",
  "id": 123456,
  "public_repos": 12,
  "followers": 203
}
All formatted, syntax-highlighted, and copy-pasteable.
What I Learned
1. You don't need React for everything
Vanilla JS is underrated. No node_modules, no webpack, no hydration delays. The entire app is < 50KB.
2. Vercel is absurdly easy
Push to GitHub → auto-deploy → custom domain in 2 clicks. I spent more time writing the README than configuring deployment.
3. Developer experience matters
The difference between "it works" and "it's delightful" is:
A loading spinner that doesn't lie
Error messages that tell you why CORS failed
Response time in milliseconds
What's Next
[ ] Save request history in localStorage
[ ] Import/export Postman collections
[ ] Response time graphing
Star the repo to follow along — I ship updates weekly.
Try It / Contribute
🔗 Live App: api-sisyphus.vercel.app
⭐ GitHub Repo: github.com/YOUR_USERNAME/api-sisyphus
🐛 Found a bug? Open an issue — I respond within 24 hours.
What's your go-to API testing tool? curl? Postman? Insomnia? Drop a comment below 👇
plain

---

## Why the Text Looked "Too Big"

You probably pasted the **front matter** (`---` block with `title:`, `tags:`, etc.) into the body. Dev.to renders that as giant text because:
- The `#` in markdown becomes a **heading** (big text)
- The `---` becomes a horizontal rule

**dev.to handles metadata separately** — use their sidebar fields, not markdown front matter.

---

## Preview Check

Before publishing, click **"Preview"**. You should see:
- Normal paragraph text (not giant)
- `##` headings as medium-sized section titles
- Bullet points as actual lists
- Code blocks with syntax highlighting

If anything still looks weird, take a screenshot of the preview and I'll fix it.

Ready to paste? Replace `YOUR_USERNAME` with your actual GitHub username in the repo link first!

DEV Community: Fyodor Dostoevsky

I Put Linux in the Browser So You Don't Have to Install a VM

The Problem

The Solution: Web Linux

Why This Matters

The Tech Stack

A Real Example

What I Learned

I Built a Lightweight Postman Alternative Because My Laptop Was Dying

The Problem

The Solution: API-Sisyphus

Why "Sisyphus"?

How It Works

The Tech Stack

A Real Example