dcli - docker and git workflows, stremlined

Micro-service teams waste untold hours sweeping up stale containers, juggling Git resets, and hunting down “it works on my machine” gremlins; dcli compresses that busywork into three verb-heavy commands. The utility targets any developer who juggles Docker Compose stacks and multiple source repositories on a daily basis—essentially anyone who has cursed at a half-dead dev environment five minutes before stand-up.

What elevates dcli above a dusty binder full of shell aliases is its ruthless focus on single-shot outcomes. Resetting state means one shot, one story: ask for “docker clean api web” and it tears down the listed containers, purges volumes, rebuilds images, and restarts only the services you name, while keeping persistent volumes intact. Repeat the same mindset on the Git side when you tell it to “git reset develop”; the CLI fetches upstream and snaps each configured repository onto the exact branch without you ever having to open another window. It reports successes and failures in terse, colored lines, sparing you the Kubernetes-grade prose dump.

The binary is delivered via Homebrew on macOS and Linux, with direct executables for Windows, so onboarding is literally two shell commands and a version check. No setup dance, no cloud service to register—just fetch, drop in your PATH, and start pruning noise from local dev. Because the entire surface area is nine sub-commands wrapped in a Go binary, updates are equally light; a new tag shows up in the tap, you pull, done.

No pricing information is surfaced on the landing page, nor are there reference to paid tiers or enterprise licensing; the code lives in a public GitHub repository and binaries are distributed free of charge today. That leaves room for future monetization, but right now the pitch is simple: dcli trades ceremony for speed, and if you live in Docker and Git all day, that trade is convincingly one-sided.