Roy
Prebuilt Mqtt Service and Ports
Looking for some guidance. Currently have a couple different services in my project, including a postgres db, mqtt broker, a publisher and a subscriber. The mqtt broker service uses an officially hosted docker image. That service internally opens port 1883 for http mqtt communication, 8080 for ws mqtt communication, as well as other ports for misc things like 8888 has routes /health for health check and /status for a management dashboard. Right now only 8080 is exposed via Railways PORT env var and works perfectly for my web socket connections on other services.
Since I can only expose one port via railway does that mean it’s impossible to take advantage of those other pieces? I’m open to any sort of strategy, but don’t know if I could handle modifying the source of the broker itself so would prefer a different option than that
Thanks!
23 replies