About BashSnippets
Who runs it
BashSnippets is a free bash script library run by Travis — a self-taught Linux developer based in Florida, publishing here and on dev.to under the handle Anguishe. Started on Ubuntu in 2013, moved through Debian and Fedora as different jobs demanded different environments, and picked up enough bash along the way to automate the repetitive parts of sysadmin work.
The site started because I kept re-writing the same scripts. Disk monitoring. Log cleanup. Service watchdogs. The third time I wrote a disk space checker, I decided to document it properly instead of burying it in ~/scripts. That folder became this site.
Everything here comes from real use on my own servers and test boxes — scripts I've run, broken at least once, and fixed. The explanations exist because I spent time figuring out why the standard one-liners fail on edge cases: the wrong partition, macOS df output formatting, cron's minimal PATH. Rather than explain that again, I wrote it up once.
Every script on the site lives in the open at github.com/anguishe/bashsnippets — the same tested versions you read here, free to clone, read, and run.
Why bash?
Bash runs on every Linux server without anything installed. Scripts that depend on Python virtual environments, Node.js, or Ruby introduce dependency problems on servers that don't have those runtimes or have conflicting versions. A bash script is a text file. Any sysadmin can read it, audit it, and run it in under a minute.
The constraint of keeping things in bash also forces clarity. If you can't implement something cleanly in bash, that's often a sign the script is trying to do too much. The right answer is usually a smaller, focused script rather than a bash script pretending to be an application.
How scripts are tested
Every script on this site passes ShellCheck before it goes up, and the outputs pasted on newer pages come from real runs on Kali Linux with bash 5.3. macOS notes flag where the bash 3.2 macOS ships from 2007 is missing features these scripts rely on — install Homebrew's bash 5.x there.
I test the failure cases, not just the happy path. The "Common Mistakes" sections on each page come from things that actually broke during testing. Scripts that don't behave correctly under failure conditions don't make it onto the site.
What's on the site
68 bash scripts
Copy-paste ready, plain-English explanations
14 interactive tools
Cron builder, chmod calc, exit code lookup
Zero logins
No account, no email, no paywall
MIT licensed
Use the scripts anywhere, including production
Stack
Static HTML migrated to Next.js 15 with TypeScript and MDX. Hosted on Vercel. Scripts are ShellCheck-clean, and the outputs pasted on the site come from real runs on Kali Linux (bash 5.3). The site has no database — snippet content lives in MDX files, and the interactive tools are React components rendered client-side.