9dc3a169b3
Co-authored-by: Thales Macedo Garitezi <thalesmg@gmail.com> Co-authored-by: Stefan Strigler <stefan.strigler@emqx.io> Co-authored-by: Zaiming (Stone) Shi <zmstone@gmail.com> Several bridges should be able to share a connector pool defined by a single connector. The connectors should be possible to enable and disable similar to how one can disable and enable bridges. There should also be an API for checking the status of a connector and for add/edit/delete connectors similar to the current bridge API. Issues: https://emqx.atlassian.net/browse/EMQX-10805 |
||
|---|---|---|
| .. | ||
| etc | ||
| include | ||
| src | ||
| test | ||
| .gitignore | ||
| README.md | ||
| rebar.config | ||
README.md
EMQX Dashboard
This application provides access to the EMQX Dashboard as well as the actual,
underlying REST API itself and provides authorization to protect against
unauthorized access. Furthermore it connects middleware adding CORS headers.
Last but not least it exposes the /status endpoint needed for healtcheck
monitoring.
Implementation details
This implementation is based on minirest, and relies on hoconsc to provide an
OpenAPI spec for swagger.
Note, at this point EMQX Dashboard itself is an independent frontend project and is integrated through a static file handler. This code here is responsible to provide an HTTP(S) server to give access to it and its underlying API calls. This includes user management and login for the frontend.