Allow non-HTTP port forwarding
in progress
Angelo Saraceno
in progress
Technically some of the provisions here have been completed: we now allow you to expose TCP ports on Railway however, we are hard at work supporting UDP (which is the underlying protocol behind HTTP/3)
No timeline for UDP but TCP is LIVE: https://docs.railway.app/deploy/exposing-your-app#tcp-proxying
Raphaël QUEIROZ
We really need UDP!
Warden
Option to host your own MQTT Server, mosquitto
T
Thomas Cahill
Warden: Hey, We do have a HiveMQ template, which is a MQTT server. We have used it internally.
Divlo
Indeed, it would be really useful!
Angelo Saraceno
Adding a comment that this effort should cover better WebSocket support and gRPC connections. More on this soon.
Angelo Saraceno
Merged in a post:
email server service
Warden
Option to host you email server? That would allow us to host everything under same hat 😁
Angelo Saraceno
Merged in a post:
Support arbitrary protocols / ports
Sean Aye
It would be great if railway allowed exposing non-http services on an arbitrary port. This would make databases like edgedb viable as they sit on top of Postgres. The docker container runs fine but I cannot connect because the connection to the db is not http
Leo Petrucci 🎱
This is essential for using stuff like PgBouncer, which is kind of the only way to use Postgres with serverless architecture.
Bruno
This would be helpful for microservices architecture. There're frameworks that supports TCP like Nestjs (https://docs.nestjs.com/microservices/basics)
Aleks Rūtiņš
Load More
→