emqx/apps/emqx_bridge_mqtt
Andrew Mayorov 44b4205561
fix(secret): do not treat missing file secrets as config error
They are intended to be used mostly in the context of resources, which
have their own feedback mechanism: statuses, retries, etc.

Also turn the error into a throw exception, so that it can be
interpreted as a regular error condition, for example by the resource
manager.
2023-10-26 14:37:14 +07:00
..
src feat(mqttbridge): support file-sourced secrets as passwords 2023-10-24 16:24:52 +07:00
test fix(secret): do not treat missing file secrets as config error 2023-10-26 14:37:14 +07:00
README.md chore(mqttbridge): add README 2023-05-30 17:56:35 +03:00
rebar.config fix(mqttbridge): ensure elixir release assembles successfully 2023-05-30 17:56:35 +03:00

EMQX MQTT Broker Bridge

This application connects EMQX to virtually any MQTT broker adhering to either MQTTv3 or MQTTv5 standard. The connection is facilitated through the MQTT bridge abstraction, allowing for the flow of data in both directions: from the remote broker to EMQX (ingress) and from EMQX to the remote broker (egress).

User can create a rule and easily ingest into a remote MQTT broker by leveraging EMQX Rules.

Documentation

  • Refer to Bridge Data into MQTT Broker for how to use EMQX dashboard to set up ingress or egress bridge, or even both at the same time.

  • Refer to EMQX Rules for the EMQX rules engine introduction.

HTTP APIs

Several APIs are provided for bridge management, refer to API Docs - Bridges for more detailed information.

Contributing

Please see our contributing guide.

License

Apache License 2.0, see LICENSE.