6 ms·

I believe the RabbitMQ management plugin is what you need, provides HTML user interface and HTML API. The BQL plugin, which is now sadly unsupported by the Rab

I believe the RabbitMQ management plugin is what you need, provides HTML user interface and HTML API. The BQL plugin, which is now sadly unsupported by the Rabbits, used to be a nice command line interface, it is a shame it is no longer supported.

AmrMostafa 15y ago
The RabbitMQ management plugin does provide an excellent command line interface. You download it along with its docs right from the management UI (/cli). Btw, I'm using RabbitMQ, and I love it. My needs do not include high load or high availability though so I can't speak for that. So what's nice about it? AMQP (you automatically get lots of tools, docs, "expectations", etc), very friendly and active mailing lists, small & clean code base, small footprint, simple, active (more features are always being added). What I don't like about RabbitMQ? While it's FLOSS inside out, its development isn't exactly a "community" work. For example, I can't report an issue, attach a patch, and receive a reviewer/committer feedback about it and possibly get it in. In fact, I can't even report an issue into their issue tracking system -- I just have the mailing list. That said, I believe they said they are going to fix that part "soon".
- rabbitmq 15y ago
  We have always accepted server patches via the mailing list: https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq... But it's true that the community has been much more involved in clients like Pika, for example. And yes we are planning to open up the bug tracker. A piece of advice for anyone doing an open source project - start with an open tracker, because opening up a previously closed tracker is a royal pain in the butt.
  - dpw 15y ago
    And while we don't use github internally, people can and do submit issues and pull requests there: https://github.com/rabbitmq https://github.com/rabbitmq (N.B. we need contributors to sign a contributor agreement.) David (rabbiteer)
rabbitmq 15y ago
Tim, what do you think is cool about BQL that might be needed in the future?

AmrMostafa 15y ago

The RabbitMQ management plugin does provide an excellent command line interface. You download it along with its docs right from the management UI (/cli). Btw, I'm using RabbitMQ, and I love it. My needs do not include high load or high availability though so I can't speak for that. So what's nice about it? AMQP (you automatically get lots of tools, docs, "expectations", etc), very friendly and active mailing lists, small & clean code base, small footprint, simple, active (more features are always being added). What I don't like about RabbitMQ? While it's FLOSS inside out, its development isn't exactly a "community" work. For example, I can't report an issue, attach a patch, and receive a reviewer/committer feedback about it and possibly get it in. In fact, I can't even report an issue into their issue tracking system -- I just have the mailing list. That said, I believe they said they are going to fix that part "soon".

rabbitmq 15y ago
We have always accepted server patches via the mailing list: https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq... But it's true that the community has been much more involved in clients like Pika, for example. And yes we are planning to open up the bug tracker. A piece of advice for anyone doing an open source project - start with an open tracker, because opening up a previously closed tracker is a royal pain in the butt.
- dpw 15y ago
  And while we don't use github internally, people can and do submit issues and pull requests there: https://github.com/rabbitmq https://github.com/rabbitmq (N.B. we need contributors to sign a contributor agreement.) David (rabbiteer)

rabbitmq 15y ago

Tim, what do you think is cool about BQL that might be needed in the future?