Surprisingly enough, by doing small cirurgical changes in the existing
EMQX control scripts, we are able to get it running with Elixir and
with existing functionalities (`console`, `remote_console`, `start`,
`stop`, `ctl`, `foreground`, `eval`).
* feat(authorization): add authorization api
* feat(authorization): add check function
* feat(authorization): use hocon config file
* feat(authz): add mysql connector
* feat(authz): support pgsql
* feat(connector): support redis
* chore(authz): use "publish/subscribe/all" instead of "pub/sub/pubsub"
Prioro to this change, ekka lib dir was added by inspecting
the ekka lib version in persisted RELEASES file.
However, this file may not be the true version if a hot
upgrade failed in the middle.
In this fix, it reads the per-version emqx.rel file
content to load lib paths.
And move emqx app back to root level
After realising the challenges of developing plugins in standalone
rebar projects. it is perhaps more smooth to keep using emqx as
a rebar dependency
Thales Macedo Garitezi