tragiccode/busly-cli repository overview

⁠Overview

Busly CLI is a lightweight, open source command-line tool that allows developers to send messages to an NServiceBus endpoint at the power of their fingertips — no boilerplate code, no host applications, just quick and reliable messaging from your terminal.

Built for speed and simplicity, this tool streamlines common messaging, testing, and debugging scenarios when working with NServiceBus and message-driven architectures. Busly CLI is fully cross-platform, running on Windows, macOS, and Linux, and offers multiple installation options to suit your workflow. Whether you’re validating endpoints, simulating events, or quickly implementing a proof of concept (POC) for a new messaging solution, this CLI lets you publish or send messages instantly, giving you full control of your distributed system from the command line.

⁠Key Features

• 🚀 Send messages via CLI – Quickly send commands or publish events to NServiceBus endpoints.
• 🧩 Supports custom message types – Define and send serialized payloads that match your message contracts.
• 🌐 Supported transports – Works with Azure Service Bus, RabbitMQ, and AWS SQS.
• ⚙️ Transport configuration file – Configure and easily switch between multiple transports. Transports can run on your local machine or be pointed to development, staging, or production environments.
• 💻 Cross-platform support – Works seamlessly on Windows, macOS, and Linux.
• 📦 Multiple installation options – Install via Chocolatey, Docker, .NET tool (via NuGet), or by downloading the binary directly from GitHub Releases.

⁠Docs

Under Construction. Stay tuned.

⁠Disclaimer

This project is not affiliated with, endorsed by, or sponsored by Particular Software. NServiceBus is a registered trademark of Particular Software.

⁠Contributing

1. Fork it ( https://github.com/tragiccode/busly-cli/fork⁠ )
2. Create your feature branch (git checkout -b my-new-feature)
3. Commit your changes (git commit -am 'Add some feature')
4. Push to the branch (git push origin my-new-feature)
5. Create a new Pull Request