Dev Ops Guide
Describe a Linux problem and get safe commands, flag explanations, a risk level and the next troubleshooting steps.
A short companion for Dev Ops: when it is useful, what it expects, and what to check before using the result.
What it does
A troubleshooting companion for Linux servers. Describe the problem in plain language — which process is using port 8080, disk is full, nginx returns 503 — and it finds the matching command, explains every flag, rates how risky it is and suggests what to check next. There is also an analyzer: paste the output of df, free, ss, docker ps, nginx -t, systemctl status or journalctl and it reads the output back to you. Everything runs in your browser; nothing is uploaded, and a search that looks like it contains a secret is kept out of the URL.
Use the tool
Open Dev Ops, add the input the tool asks for, run it, and check the output before using it elsewhere.
Input and output
- Input: text.
- Output: text.
- Category: DevOps.
Privacy and processing
Processing happens locally in your browser. This tool does not upload the input to ilham.dev.
Common use cases
- check which process uses a port
- find what is filling the disk
- debug an nginx 502 or 503
- inspect a crash-looping Docker container
- read journalctl and systemctl output
- check memory pressure and swap
Questions
Does it run the commands for me?
No. It only suggests commands and explains them; you copy the one you want and run it yourself. That is deliberate: a tool that can run anything on your server is a tool that can break your server.
Is my search sent anywhere?
No. The catalog, the search index and the analyzer all run in your browser. Nothing is uploaded, and if a search looks like it contains a secret — a token, a password, a private key — it is kept out of the URL too.
What can the analyzer read?
Paste the output of df, free, ss, docker ps, nginx -t, systemctl status, lsblk, git status, ps, top, pvs, or MySQL and PostgreSQL status output. It detects the format, points out the lines that matter and suggests the next command.
Are the suggested commands safe?
Each command is labelled safe, changes state, or dangerous, and destructive ones are explained before you run them. Still read the command and its flags before pasting it into a production shell.
Related guide
For broader background, see Linux Command Line Tasks Without Surprises.