|
|
1 ano atrás | |
|---|---|---|
| .. | ||
| include | 46877e979b chore: update copyright-year | 2 anos atrás |
| src | 7ca5205f3f feat: add `peername` to rule events that already have `peerhost` | 1 ano atrás |
| test | 4f341bef8b Merge pull request #12920 from cisiqo/patch-6 | 1 ano atrás |
| .gitignore | 0a62d6c556 refactor(gw): rename all gateway application name | 3 anos atrás |
| README.md | 0a62d6c556 refactor(gw): rename all gateway application name | 3 anos atrás |
| mix.exs | 19f3b030f9 chore: preparing to run common tests / eunit with mix | 1 ano atrás |
| rebar.config | 5e100f52b8 style: erlfmt all `rebar.config` files and `bin/nodetool` | 2 anos atrás |
The Stomp Gateway is based on the Stomp v1.2 and is compatible with the Stomp v1.0 and v1.1 specification.
In EMQX 5.0, Stomp gateway can be configured and enabled through the Dashboard.
It can also be enabled via the HTTP API or emqx.conf, e.g. In emqx.conf:
gateway.stomp {
mountpoint = "stomp/"
listeners.tcp.default {
bind = 61613
acceptors = 16
max_connections = 1024000
max_conn_rate = 1000
}
}
Note: Configuring the gateway via emqx.conf requires changes on a per-node basis, but configuring it via Dashboard or the HTTP API will take effect across the cluster.
More documentations: Stomp Gateway