Articles

I've been running cfExec.com for a while now, and it's up and running today. It's a reference site for command-line tools you can drive from ColdFusion: what each one does, live "try it" demos, the arguments spelled out. The one thing it never did was hand you the code in one place. Now it does. The CFC library behind the site is up on GitHub at https://github.com/JamoCA/cfExec.

Here's what you get: a base cfExec.cfc and 91 wrapper components, one per tool. Each wrapper extends the base, knows where its executable lives, and gives you typed methods. You call a method instead of hand-building a cfexecute call and squinting at stdout afterward.

The tools are grouped the same way they are on the site, by what they do:

• Admin: appcmd, taskkill, WMIC
• Archive: 7-Zip, HTTrack, Monolith
• Cloud: rclone, S3Express, WinSCP
• Converter: html2markdown, Pandoc, wkhtmltopdf
• Database: Database .NET, DbVisualizer, DuckDB, OctoSQL, SQLite
• File Search: diskus, fd, FileList, FileLocator Pro, grepWin, HashConsole, SearchMyFiles, ripgrep, TrID
• File System: Bulk Rename Command, DeleteFiles, FastCopy, FNR, gsar, Robocopy
• Image: caesiumclt, GraphicsMagick, ImageMagick, pingo, Tesseract OCR, wkhtmltoimage, Zint
• Metadata: ExifTool, Exiv2, Kid3, MediaInfo, pdfinfo
• Network: aria2, cURL, CyberDuck CLI, dog, Globalping CLI, http-ping, Obscura, trurl, Wget
• PDF: Foxit Reader, Ghostscript, pdfcpu, pdfdetach, pdffonts, pdfimages, PDFtk Server, pdftohtml, pdftopng, pdftotext, qpdf
• Runtime: Adobe ColdFusion CLI, BoxLang, CommandBox, Java, jcmd, Node.js, Python, Ruby
• Security: Bitwarden, Gitleaks, SSL Labs Scan, TruffleHog
• Stats: hyperfine, Tokei
• System: duf, Fastfetch, PsExec, PsKill, schtasks, SigCheck
• Text: cloc, CSVFileView, jq, Markdown Monster, Miller, tabspace, yq

That's 16 categories and 91 tools today, and the list grows as I wrap more.

The components carry their own metadata, too: name, category, license, project URL, last known version. If you want to build your own catalog page or a version check, it's all readable at runtime.

One thing about paths. The wrappers default to c:\cli\<tool>\<exe>. If your binaries live somewhere else, pass exePath to the constructor and you're set. That default is the only thing that assumes a location, and you can override it per call.

Why a separate repo instead of just pointing people at the site's source? Because the site repo is full of things you don't need in order to use the library: the website templates, the demo harness, build scripts, sample files. The GitHub repo is only the CFCs, the per-tool docs, and a README. Copy the CFCs folder into your project and you're running. Nothing to resolve, nothing to install through a package manager.

If you've spent years copy-pasting cfexecute snippets out of old projects every time you needed to shell out to something, this is that habit cleaned up and kept in one place. Pull it down, point the paths at your install, and tell me if there's a tool you use that I haven't wrapped yet.

The live site is at https://www.cfExec.com/ and the code is at https://github.com/JamoCA/cfExec.