Skip to content

Releases: mod-bee/modbee-mqtt

Release list

modbee-mqtt 0.1.0

modbee-mqtt 0.1.0 Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 27 Oct 03:34
v0.1.0
990e317

The first release: the library for boards and hosts, and modbee-mqtt, the server
built from it, as downloads for Linux and Windows and as a Docker image.

The library

  • MQTT 5.0 and 3.1.1 in C++14, with nothing that waits on the network: a
    client, a broker and a bridge, the same source on a board and a host.
  • MqttDevice, typed values, Sparkplug B (an edge node and a host
    application, tested with the Eclipse Sparkplug TCK).
  • Boards: ESP32, ESP8266, mbed (Portenta, Opta, Nano 33), RP2040, STM32 - over
    Wi-Fi, Ethernet or cellular, with TLS on each.

The server

  • modbee-mqtt serve: one broker per CPU core behind one port, configured with
    one modbee.yaml; sessions and retained messages that survive a restart;
    device logins and provisioning.
  • The Kafka pipe: MQTT to Kafka and back, messages passed through untouched,
    a PUBACK only once Kafka has the message.
  • The Application API, gRPC with a REST admin surface: consumer groups that
    share a device's messages, publishing to devices, connections, sessions,
    retained messages and logins - on a Unix socket, or TCP with a token.
  • Linux (x86-64, ARM64) and Windows (x86-64), as a service on both.

Ready to run

  • .deb and .rpm packages, x86-64 and ARM64.
  • Set up with the modbee-mqtt command alone, the same on Linux and Windows:
    modbee-mqtt service install runs it as a service (systemd, or a Windows
    service) keeping everything in one folder, and modbee-mqtt admin sets the
    admin login. No configuration file.
  • modbee-mqtt for Linux as one static binary that runs on any distribution, and
    modbee-mqtt.exe for Windows as one file - each with the broker, the Kafka pipe,
    the Application API and the CLI inside; modbee-mqtt --version lists them.
  • Each attested by GitHub, with a CycloneDX SBOM, and a checksum list signed
    with Sigstore. docs/releases.md
    shows how to check one.
  • The Docker image: ghcr.io/mod-bee/modbee-mqtt:0.1.0, amd64 and arm64.

Downloads

For x86-64 ARM 64-bit (Raspberry Pi 4/5, ARM servers)
Debian, Ubuntu modbee-mqtt_0.1.0-1_amd64.deb modbee-mqtt_0.1.0-1_arm64.deb
RHEL, Rocky, Alma, Fedora modbee-mqtt-0.1.0-1.x86_64.rpm modbee-mqtt-0.1.0-1.aarch64.rpm
Any Linux: one file, nothing to install modbee-mqtt-0.1.0-linux-x86_64 modbee-mqtt-0.1.0-linux-arm64
Windows: one file, also a Windows service modbee-mqtt-0.1.0-windows-x86_64.exe
Docker ghcr.io/mod-bee/modbee-mqtt:0.1.0 the same tag 
sudo apt install ./modbee-mqtt_0.1.0-1_amd64.deb     # or: sudo dnf install ./modbee-mqtt-0.1.0-1.x86_64.rpm
sudo modbee-mqtt service install                         # runs it as a service; Windows: the same
sudo modbee-mqtt admin                                   # the admin login

Each is the broker, the Kafka pipe, the Application API and the CLI;
modbee-mqtt --version lists them. The .cdx.json files are each binary's SBOM:
every library inside, with its version and licence.

Checking a download

gh attestation verify modbee-mqtt_0.1.0-1_amd64.deb --repo mod-bee/modbee-mqtt

or against SHA256SUMS, signed with Sigstore - docs/releases.md.

Assets 14