DEV Community: raymonepping

🐳 Slim, Scan, Ship Your Docker Containers – Fully Automated

raymonepping — Fri, 01 Aug 2025 06:00:15 +0000

Introduction

Ever feel like your Docker images are getting bloated, full of secrets, or just generally out of control?
Yeah, I’ve been there. So I built a Homebrew-installable CLI that optimizes, hardens, scans, and ships your Docker images—in one sweep.

—-

🚀 What’s Inside?

• Image slimming with docker-slim
• Automated scanning (Trivy, Grype, Dive, Hadolint, and more)
• Push to Docker Hub—auto-tagged and multi-arch
• Markdown logs and reporting for your CI/CD pipelines

—-

🧑‍💻 Read the full story, the how, and grab the tools:

👉 “🐳 Slim, Scan, Ship Your Docker Containers

No more wrestling with scripts or fighting your build pipeline.

🧠 Introducing `brew_brain`: The Homebrew Arsenal Manager I Wish I Had Years Ago

raymonepping — Mon, 21 Jul 2025 19:36:43 +0000

If your terminal is a little too full of Homebrew installs, and you’re tired of forgetting what’s actually important, this is for you.

🍺 The Problem

Ever run brew list and felt a wave of guilt?

“Wait, do I even use half of these? Why is that still installed?”

Worse, have you ever needed to:

Onboard a teammate and document your dev setup?
Move to a new Mac and wish you could just “import your tools” (without 100+ random things)?
Prove to security/audit teams what’s actually on your machine?

Me too. That’s why I built brew_brain — a Bash-powered Homebrew arsenal manager that tracks what matters, documents it, and lets you export or audit your toolkit in seconds.

🚀 What `brew_brain` Actually Does

Track only what matters: Add "track": "true" in your arsenal JSON to focus on your must-have CLIs.
Instant health checks: brew_brain checkup tells you what’s missing, outdated, or gathering dust.
Templated Markdown & JSON output: Generate clean, team-friendly docs (thanks, .tpl files!) or export pretty JSON for backups or onboarding.
One-liner installs: If you’re missing a tool, brew_brain will even suggest (or run) the right brew install.

🛠️ How to Use It

Clone or drop in $PATH: Just grab the script, put it in your $PATH, and you’re set.
Configure your arsenal: Your Homebrew arsenal lives in a simple JSON file (~/.brew_brain.json). Only “tracked” tools get included in audits or docs.
Audit & document with a single command:
- brew_brain → Markdown summary
- brew_brain checkup → Health check
- brew_brain --output json --output-file arsenal → Export for backup/onboarding
- brew_brain --dump --filter=raymonepping --output=my_brews.json → Full, pretty, filtered export

Bonus: Markdown docs use your own .tpl template files, so you can make the docs fit your style or team branding.

⚡️ Real-World Uses

Team onboarding: Ship a single JSON config and every dev has the same CLI arsenal in minutes.
Compliance or “works on my machine”: Export a clear, timestamped doc of exactly what’s installed.
Disaster recovery/migration: Moving to a new Mac? Grab your arsenal JSON and re-create your setup—minus the cruft.

🤔 Why Not Just Use `brew list`?

Because brew list is just a list.

brew_brain is an arsenal—tracked, documented, exportable, and team-ready.

You control what gets tracked, how it’s output, and how it’s shared.

Plus, you get Markdown docs that look… actually decent.

🧑‍💻 Try It!

Install, track, document, and ship your toolkit like it actually matters.

🌳 Automating Project Structure Insights with Folder_Tree

raymonepping — Sat, 19 Jul 2025 13:40:07 +0000

Map. Clean. Document. Repeat.

Because folder structure is documentation — and now, it’s automated.

🧠 Why I Built folder_tree

Every time I opened an old project folder, I saw the same mess:
Too many files, deeply nested modules, ignored clutter, and no clear overview.

So I wrote folder_tree — a CLI that visualizes, filters, and documents any folder tree in seconds.
It’s minimal, scriptable, and designed to run in CI/CD or your local terminal.

Because sometimes you just need to see the shape of things.

⚙️ What It Does

✅ Outputs your folder tree in Markdown
✅ Excludes noise automatically (.terraform/, node_modules/, .DS_Store/, etc.)
✅ Respects .treeignore files and presets
✅ Optionally includes hidden files like .env, .git
✅ Counts total files/folders + disk usage
✅ Templated, versioned, and Homebrew-installable

🚀 Quickstart

brew tap raymonepping/folder-tree-cli
brew install raymonepping/folder-tree-cli/folder-tree-cli

folder_tree --preset terraform --output markdown

Need hidden files or disk size?

folder_tree --hidden --compute --output markdown

Set a custom config (optional):

export FOLDER_TREE_HOME=/opt/homebrew/opt/folder-tree-cli/share/folder-tree-cli

✨ Example Output

📂 Target: my_project
🛡️ Excludes from: .treeignore
./
├── bin/
│   └── folder_tree*
├── tpl/
│   └── folder_tree_md.tpl
├── README.md
└── FOLDER_TREE.md

5 directories, 10 files
📦 Total: 107.6 KB

💡 Use Cases

🧱 Document structure in your README.md
🚀 Auto-generate folder views for GitHub projects
📁 Catch bloated or outdated folders at a glance

🧬 Under the Hood

Modular template system (tpl/)
.treeignore and --preset for dynamic filtering
Markdown or terminal output (--output markdown)
Git-tracked file mode (--git)
Supports --compute, --history, --verbose, --bump-version

🔚 Final Thoughts

You don’t need another pretty tree diagram.
You need a clean, structured snapshot of your project — ready for docs, reviews, or CI logs.

And now you’ve got one.

📦 Grab it from GitHub (https://raw.githubusercontent.com/raymonepping/homebrew-folder-tree-cli/refs/heads/main/bin/folder_tree)

🧠 Built for clarity. Documented by default.

🕊️ Quote to remember:
“Structure isn’t boring — it’s your first line of clarity.”

Want to read more about folder_tree?

📘 medium.com article: Automating Project Structure Insights with Folder_Tree

📗 medium.com article: From ASCII Art to Audit-Ready Docs

🏷️ commit_gh: Because Git Tags Shouldn't Be That Hard"

raymonepping — Sat, 19 Jul 2025 13:19:40 +0000

“A no-nonsense CLI that automates commits, tags, and version bumps — and finally makes semantic versioning behave like it should.”

Automation should automate itself — and versioning shouldn't feel like a tax.

You ever forget to tag a Git commit, or bump the version number manually, or mistype something in the changelog?

Yeah — me too.

That’s why I built commit_gh.

It's a Bash-based CLI that:

Commits your changes ✅
Tags them semantically ✅
Pushes everything ✅
And verifies it all actually worked ✅

Because I was done losing minutes to versioning drama.

🚀 Quickstart

brew install raymonepping/commit-gh-cli/commit-gh-cli

Then just:

commit_gh --bump patch --verify

This bumps the version, commits changes, creates a Git tag like v1.2.3, and pushes it to origin/main.

—-

🔧 What It Does (in one command)

commit_gh --bump patch --verify

Checks if your working tree is clean 🧼
Pulls + rebases from main 🔄
Commits and pushes any changes 📦
Bumps the patch version via .version (or creates one if missing) 🧮
Tags and pushes the new version to Git 🏷️
Verifies everything (branch, tag, version file) ✅

—-

🧰 Why I Built This

Because git commit is easy.
But everything around it — tagging, syncing, bumping — gets annoying fast in real workflows.

I wanted:

A single command to do it all
Safety checks before publishing
Homebrew installability for all my CLIs

⸻

✅ Benefits

Semantic versioning baked in
Verification mode: --verify
Self-healing .version file
GitHub tag sync
Designed for CI/CD or local use
Easily extendable

⸻

📦 Want to Package Your Own CLI?

I wrote this to automate versioning for my own Homebrew-packaged tools like:

folder_tree 🗂️
repository_audit 🔍
repository_backup 🛡️

Now commit_gh powers all of them — keeping tags, versions, and changelogs in sync.

⸻

🤖 TL;DR

If you’ve ever run git tag, realized you forgot to bump the version, re-tagged, then force-pushed… this tool is for you.

⸻

Check it out:
🔗 GitHub – commit_gh_cli
🍺 brew install raymonepping/commit-gh-cli/commit-gh-cli
📖 commit_gh --help

⸻

Built for engineers. By an engineer who got tired of typing the same commands over and over.

🤖 Teaching the Cyborg to Document: Auto-Generated README.md’s with Style

raymonepping — Tue, 15 Jul 2025 20:10:57 +0000

🧠 Why I Built This

Let’s be honest: Documentation is usually an afterthought.
We ship the CLI, tag the release, maybe slap a README together — and then… forget about it.

But for a growing suite of modular, Homebrew-packaged Bash CLIs (like folder_tree, repository_backup, radar_love…), that pattern falls apart fast. Outdated docs? Broken install steps? Yuck.

I wanted:

Docs that feel personal and consistent
Documentation that stays up-to-date by default
The ability to inject quotes, visuals, and folder trees — without manual edits
To make the docs look good, because… tools that look good get used!

So I built: self_doc.sh.

TL;DR:
I automated my CLI documentation with Bash and modular templates, so every release ships with an up-to-date, beautiful README.md. Here’s how.

🛠️ What Does self_doc.sh Do?

Auto-detects your CLI’s binary, version, and metadata

Loads optional CLI-specific .cli.vars for easy customization

Uses modular Markdown templates (like readme_header.tpl, readme_quote.tpl, etc.)

Generates a clean, attractive README.md file — ready to commit or publish

Falls back gracefully if visual tools like folder_tree aren’t installed

Injects warnings and install hints automatically

Runs anywhere: No dependencies outside Bash + coreutils

It’s like a little CI pipeline for your docs — but it’s fast, local, and always in sync.

📦 Template-Driven Docs

Instead of one big heredoc, self_doc.sh leverages a folder of template snippets:

tpl/
├── readme_01_header.tpl
├── readme_02_project.tpl
├── readme_03_structure.tpl
├── readme_04_body.tpl
├── readme_05_quote.tpl
├── readme_06_article.tpl
└── readme_07_footer.tpl

Templates use smart placeholders:

{{FOLDER_TREE}} ← replaced by a live tree view

Just reorder, remix, or reuse template files across projects. Zero lock-in.

🌳 Smart Fallbacks: folder_tree vs. tree

If you have the folder_tree CLI installed, the README gets emoji-rich, beautiful output.
No folder_tree? It falls back to tree.

No tree either? You get this in your docs:

❌ No tree tool available! Install either folder_tree or tree for full functionality.

No conditionals needed in your templates. No manual fixes. It Just Works™.

✨ Features at a Glance

✅ Full CLI arg parsing (long + short flags)
🧠 Auto-discovers CLI binary + version
🧱 Modular template support (with fallback)
💬 Helpful errors if a template file is missing
📁 Dynamic folder structure rendering
🚫 Dry-run and quiet modes for scripting/CI
🍺 Homebrew-link and quote injection via .cli.vars
🧽 Cleans emoji/ANSI codes from folder trees
🔧 One-liner install suggestions if missing dependencies

📄 Example Output

Here’s a real snippet from an auto-generated README:

🌳 folder_tree  
CLI tool that visualizes and documents folder structures

Version: 1.0.5

> ⚠️ folder_tree CLI not found. This structure was generated using standard `tree` as fallback.
> To install folder_tree: `brew install raymonepping/folder-tree-cli/folder-tree-cli`

./
├── bin/
│   └── folder_tree
├── lib/
│   ├── folder_tree_utils.sh
│   └── self_doc.sh
└── tpl/
    └── readme_*.tpl

You get context, usage, and install hints — all without hand-writing Markdown.

🔍 Where I Use It

This one script now powers the docs for:

folder_tree — structure-aware CLI
radar_love — secret leak simulation for Vault Radar
repository_audit — audit all the Git repos in your folders
repository_backup — safe, modular, Homebrew-ready backup CLI

They all document themselves.
One command. No drift.

📈 Zero-Drift Docs — For Real

Once installed (Homebrew or manual), just point self_doc at your project. Examples:

# In a project folder with ./bin/my_cli:
self_doc

# To use templates from another repo:
self_doc -t ./x/tpl -f ./x/bin/y

No guessing. No copying output.
Just a live README that always matches your code.

🧪 Real-World Value

This is more than just pretty READMEs:

Keeps your repos hygienic (especially when you have dozens)
Makes it easy for others to fork/contribute
Onboarding? Instant context.
Reinforces a culture of automation — even for docs

🧰 Get Started!

Want to automate docs for your own Bash CLI project?
Clone it the old-school way:

curl -O https://raw.githubusercontent.com/raymonepping/folder_tree_cli/main/lib/self_doc.sh
chmod +x self_doc.sh
./self_doc.sh --tpl-dir ./tpl --outfile README.md

Or, the Homebrew way (for easy updates):

brew install raymonepping/self-doc-gen-cli/self-doc-gen-cli
brew upgrade self-doc-gen-cli    # To update later
self_doc --help

Homebrew keeps you up to date, everywhere.

🔚 Final Thoughts

Docs don’t have to be dull. Or manual. Or outdated.
With the right automation, they’re a first-class citizen of your CLI — a mirror of your code.

self_doc.sh isn’t just a helper script. It’s your CLI’s reflection.

So…

Build your CLIs. Let them document themselves.

It’s Bash, top to bottom. No YAML hell. No Node/Go runtimes.
Just you, your logic, and docs that never drift.

📦 Grab the Script + Templates

Check it out on GitHub:
👉 https://github.com/raymonepping/folder_tree_cli/tree/main/lib/self_doc.sh

Or just grab the raw script:
👉 https://raw.githubusercontent.com/raymonepping/folder_tree_cli/main/lib/self_doc.sh

Feel free to adapt for your own projects!
Questions or feedback? Drop a comment below 👇

🆕 repository_backup updated — a modular Bash CLI for safe, versioned backups with: 🧪 Integrity checks 💥 Emergency restore 🛠️ Homebrew install: brew install raymonepping/repository-backup-cli/repository-backup-cli

raymonepping — Tue, 15 Jul 2025 14:42:05 +0000

📦 Tired of Backups That Don’t… Restore?

raymonepping — Tue, 15 Jul 2025 14:08:31 +0000

Just shipped a new update to repository_backup — a modular, DevOps-friendly CLI that actually does what it says:
• 🛡️ Safe, dry-run support by default
• 🧰 Smart .backup.json and .backupignore generation
• 🧪 Integrity checks after restore (yes, we verify!)
• 🧼 Prune, recover, and emergency restore — all from the CLI
• 🏷️ Homebrew installable and CI-ready

If your backups are just “archives” — you’re doing it wrong.
This tool is built for real-world recovery.

→ brew install raymonepping/repository-backup-cli/repository-backup-cli
→ repository-backup --help

🧠 Built for myself. Polished for others.
💬 Feedback, ideas, PRs welcome.

📦 repository_backup: A DevOps-Friendly CLI for Safe, Modular Backups

raymonepping — Tue, 15 Jul 2025 13:18:54 +0000

What started as a simple safety net is now a deeply integrated DevOps CLI:

Modular
Self-documenting
Format-aware
Homebrew-packaged

And—thanks to recent updates—even easier for everyone to use

⚡️ Why This Tool Exists

I was tired of backup scripts that were either too basic, too fragile, or never quite “safe.”

I wanted real dryrun support
I wanted declarative config — in HCL, YAML, or JSON
I wanted proper summaries, Git tagging, and backups I could trust

So, I built a Bash CLI that covers all this—and keeps evolving.

🚀 What’s New In This Release?

Output Directory Control Specify exactly where your backups are stored with --output-dir:

repository_backup --target ./my_project --output-dir ./my_backups

No more rigid folder structure—use any path, and organize backups however you like.

Built-in Interactive Wizard Run the CLI without arguments to launch a context-aware wizard:

repository_backup

The wizard walks you through backup, restore, list, prune, and summary actions—adapting prompts for clarity, so you can’t get lost.

🛡️ Quickstart

Install via Homebrew:

brew tap raymonepping/repository-backup-cli
brew install raymonepping/repository-backup-cli/repository-backup-cli

Create your first backup:

repository_backup --target ./your_project_folder

Or, for full guidance, just type:

repository_backup

Restore the latest backup (with dryrun safety):

repository_backup --target ./your_project_folder --restore-latest --dryrun

Edit what gets backed up:
The CLI auto-generates a .backup.hcl, .backup.yaml, or .backup.json—based on what you have installed (hclq, yq, etc). Just tweak it to your needs.

View summary logs:

Clean Markdown summaries are auto-written to
./backups/catalogs//backup_summary.md

🧠 What Makes This CLI Different

Declarative config: HCL/YAML/JSON—fits your stack, not the other way around

Full dryrun support: see exactly what will happen, every time

Safe pruning: manage retention, keep your backup folders clean

Git-aware: tags every backup, supports emergency restores from latest tag

MD5 integrity checks: verifies your restores—so you’re never guessing

💡 Example Use Cases

Keep your projects (or your CLI scripts) safe, versioned, and recoverable

Back up and restore with confidence—no more “restore roulette”

Use the wizard for foolproof operation, or stick to CLI flags for automation

🛠️ Under the Hood

Modular design with smart bootstrapping: creates config/folders on the fly

Markdown summaries for every backup

One-liner DevOps workflows: backup, commit, and version in a single go

🍺 Production-Ready & Open

Install via Homebrew, or explore/fork/contribute on GitHub:
github.com/raymonepping/homebrew-repository-backup-cli

Backups shouldn’t be risky. With repository_backup, they aren’t. Try the wizard or CLI today and automate your peace of mind!

👋 Hey Dev.to — I'm Raymon, and I Build Battle-Tested Bash CLIs (That Actually Do Stuff)

raymonepping — Tue, 15 Jul 2025 08:38:36 +0000

I'm a solutions engineer working in the HashiCorp ecosystem, but really, I'm just someone who enjoys turning chaos into clean automation — especially with a Bash script or two.

Most of my tools start with a personal itch:

Too many stale Git repos? I built repository_audit
Lost in my own folder structure? That became folder_tree
Want backups that actually restore? Say hello to repository_backup
Need to simulate leaked secrets for Vault Radar? That’s radar_love

All of these are Bash-based, Homebrew-installable CLIs — modular, documented, and built for CI/CD from day one. Because automation should automate itself. And also look good doing it.

🧰 Why I'm Here

Dev.to has that rare mix: technical depth without gatekeeping, and devs who genuinely want to build smarter, not louder. I’m here to share tools, document tricks, and write in a way that’s more “here’s what worked” than “let me lecture you about infrastructure.”

My writing leans practical and conversational — with a focus on:

🔧 CLI tooling
📦 DevOps flows (Terraform, Vault, Nomad, etc.)
🧠 Automation philosophy
🗂️ Keeping your repos clean, backed up, and documented

🌱 What’s Coming

In the next few posts, I’ll be sharing:

folder_tree — a Brewable CLI that turns your folder layout into Markdown docs (with presets, ignore rules, and wizard mode)
repository_backup — for Git-aware backups that won’t embarrass you when it’s time to restore
Some meta tooling (sanity_check, generate_docs, etc.) that I use across all my CLIs to keep things clean and maintainable

🎨 A Bit of Style

If my tools had a personality, it would be:

90% helpful
5% sarcastic
5% “let’s make this look good too”

—-

👉 Curious about the tools I mentioned? Head over to github.com/raymonepping and explore.

Expect emojis, Markdown, clear docs, and sometimes a cyborg image or two generated by AI for no good reason except vibes.

📫 Want to connect?

You’ll find me building DevOps demos, writing Medium articles, or overengineering my personal CLI tooling because I actually enjoy it.

Let’s build cool stuff.

— Raymon

DEV Community: raymonepping

🐳 Slim, Scan, Ship Your Docker Containers – Fully Automated

Introduction

🚀 What’s Inside?

🧑‍💻 Read the full story, the how, and grab the tools:

🧠 Introducing `brew_brain`: The Homebrew Arsenal Manager I Wish I Had Years Ago

🍺 The Problem

🚀 What brew_brain Actually Does

🛠️ How to Use It

⚡️ Real-World Uses

🤔 Why Not Just Use brew list?

🧑‍💻 Try It!

🌳 Automating Project Structure Insights with Folder_Tree

🧠 Why I Built folder_tree

⚙️ What It Does

🚀 Quickstart

✨ Example Output

💡 Use Cases

🧬 Under the Hood

🔚 Final Thoughts

📦 Grab it from GitHub (https://raw.githubusercontent.com/raymonepping/homebrew-folder-tree-cli/refs/heads/main/bin/folder_tree)

📘 medium.com article: Automating Project Structure Insights with Folder_Tree

📗 medium.com article: From ASCII Art to Audit-Ready Docs

🏷️ commit_gh: Because Git Tags Shouldn't Be That Hard"

“A no-nonsense CLI that automates commits, tags, and version bumps — and finally makes semantic versioning behave like it should.”

🚀 Quickstart

🔧 What It Does (in one command)

🤖 Teaching the Cyborg to Document: Auto-Generated README.md’s with Style

🧠 Why I Built This

🛠️ What Does self_doc.sh Do?

📦 Template-Driven Docs

🌳 Smart Fallbacks: folder_tree vs. tree

✨ Features at a Glance

📄 Example Output

🔍 Where I Use It

📈 Zero-Drift Docs — For Real

🧪 Real-World Value

🧰 Get Started!

🔚 Final Thoughts

📦 Grab the Script + Templates

🆕 repository_backup updated — a modular Bash CLI for safe, versioned backups with: 🧪 Integrity checks 💥 Emergency restore 🛠️ Homebrew install: brew install raymonepping/repository-backup-cli/repository-backup-cli

📦 Tired of Backups That Don’t… Restore?

📦 repository_backup: A DevOps-Friendly CLI for Safe, Modular Backups

What started as a simple safety net is now a deeply integrated DevOps CLI:

⚡️ Why This Tool Exists

🚀 What’s New In This Release?

🛡️ Quickstart

Restore the latest backup (with dryrun safety):

View summary logs:

🧠 What Makes This CLI Different

💡 Example Use Cases

🛠️ Under the Hood

🍺 Production-Ready & Open

👋 Hey Dev.to — I'm Raymon, and I Build Battle-Tested Bash CLIs (That Actually Do Stuff)

🧰 Why I'm Here

🌱 What’s Coming

🎨 A Bit of Style

🚀 What `brew_brain` Actually Does

🤔 Why Not Just Use `brew list`?