Skip to content

Please expose more ports by default #3

@aaron-613

Description

@aaron-613

Unless using Docker on Linux in "host" network mode, ports are not able to be opened/exposed dynamically... only when the container is created. Which means if you want to use other protocols on other ports, you need to blow away the container and recreate it.

Can we please expose a basic subset of ports to make it easy for developers to start using the broker in a multi-protocol way? E.g.: https://github.com/SolaceLabs/solace-single-docker-compose

port 8080 — Use this port when configuring the message broker container with Solace PubSub+ Manager.
port 55555 — Your applications can use Solace APIs to connect to the message broker on this port.
port 8008 — The JavaScript sample applications below use this port to pass Web Messaging traffic through the message broker.
ports 1883 & 8000 — Ports for MQTT connectivity, over TCP and over WebSockets respectively
port 5672 — AMQP 1.0 applications using Apache QPID APIs would connect here
port 9000 — Use REST to send messaging and event data with Solace’s RESTful API port
port 2222 — Use SSH to connect to the Solace Command Line Interface (CLI) for advanced configuration

This would be in Step 2 of the README, and just uncommenting certain lines of the YAML file.

Thanks!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions