Bash: Guides and Practical Know-how | Page 7 | mironsoft Blog
Bash
-
Nov 5, 2025
A shell script that spawns a thousand external processes for a thousand files isn't a performance problem, it's a design problem. Anyone who understands how much a fork costs, which operations builtins already cover, and how caching works in the shell writes scripts that take seconds instead of minutes.
-
Nov 3, 2025
The virtual /proc filesystem exports kernel internals as seemingly ordinary files. Reading /proc/[pid]/status, /proc/meminfo, and /proc/loadavg directly with built-in Bash tools produces lightweight diagnostic scripts that need no external process call and work fine in minimal container images without extra tooling.
-
Oct 25, 2025
$(...) and backticks appear to produce the same result at first glance: a command's output gets substituted somewhere else in the script. The difference only shows up with nesting, quoting, and understanding why a variable set inside the substitution vanishes without a trace afterward. This article covers both.
-
Oct 20, 2025
Container tooling like Docker and Kubernetes ships with powerful CLIs, but only Bash automation ties health checks, rollout control and alerting into a complete workflow. Teams that automate Docker and Kubernetes workflows with Bash cut down on manual intervention and make deployments traceable, repeatable and safe.
-
Oct 19, 2025
Shell scripts rarely survive code reviews without objections, because standardized checklists are simply missing. This Bash checklist covers all critical dimensions: security, error handling, logging, testability with BATS, and static analysis with ShellCheck, systematically and with a practical focus.
-
Oct 14, 2025
Anyone who investigates a broken Bash script only with scattered echo lines wastes time and loses overview. The Bash debugger bashdb brings breakpoints, watchpoints and call stack analysis into the shell and makes debugging complex scripts as traceable as in any other programming language.
-
Oct 9, 2025
Starting a script in the background with & does not make it a daemon. A true daemon detaches completely from the terminal, prevents double starts through a PID file, reacts in a controlled way to signals like SIGTERM and SIGHUP, and writes its log somewhere that stays reachable even without a terminal.
-
Oct 2, 2025
A script that simply aborts on the first 429 response is not automation, it is a ticking time bomb. Rate-limited API requests with retry in Bash respect Retry-After headers, use exponential backoff with jitter, and deliver reliable results even under strict API limits.
-
Sep 28, 2025
Unstable APIs fail in different ways: a short timeout, a 503, or sometimes no response at all. curl ships with built-in retry behavior through --retry, --retry-delay and --retry-connrefused that covers many of these cases, but understanding idempotency is what actually decides whether a retry is safe at all, without processing data twice.
-
Sep 27, 2025
Modern infrastructure delivers configuration in JSON, YAML and .env files at the same time. Anyone merging these formats in shell workflows needs robust loading, validation and export patterns, otherwise missing fields, unsafe variables and format inconsistencies turn into a silent risk in deployment pipelines.