websocket-actor-system
websocket-actor-system copied to clipboard
Vapor Support
Would you have any guidance on getting this deployed on a Vapor server?
It would be awesome to have a method to bootstrap the actor system server with Vapor's NIO internals.
I've have had success in getting Websocket Actors to communicate between a Vapor server and a client on localhost, but haven't had the same success in production. It seems the actor system server isn't sharing the port with the Vapor server, and the client throws a lot of notUpgraded errors.
It also seems like the ServerAddress implementation doesn't respect the path parameter – the client always tries to connect to the server on the root path.
Perhaps the port parameter should also be optional for cases where we connect to a server URL. I suspect part of my problem in production may be that my host (DigitalOcean App Platform) isn't accepting the explicit 443 port. I would like Websocket Actors and Vapor HTTP traffic both to go through port 8080 which the host will then proxy over SSL to 443 (host doesn't allow more than one internal port to expose).
Just posting this to see if you have any guidance or if other users faced similar issues. I'll track any updated findings here.
Thanks again for creating this library!