How to externalize the socket.io server?
I saw a previous post by someone that asked a similar question about externalizing the socket server.
I've already open up the CORS setting on my server so that any client can send their requests. The thing is that using my postman debugger on the following uri doesn't give too much information:
ws://localhost:3001
If I investigate from the client side, I see a different token generated for the client app. I suppose the client is redirected to the backend server if I see the following websocket popup in the dev panel in my browser: ws://localhost:3000/?token=iYirTHOg-k0x
After this all goes directly over localhost:3001
Can someone explain how the auth system works for websockets? and how the flow of websockets work for .wasp in frontend and backend and let me know how I can plug in my external sources?
Should I define my own websocket system to externalize? or can I use the existing tooling with minimal changes?
I've already open up the CORS setting on my server so that any client can send their requests. The thing is that using my postman debugger on the following uri doesn't give too much information:
ws://localhost:3001
If I investigate from the client side, I see a different token generated for the client app. I suppose the client is redirected to the backend server if I see the following websocket popup in the dev panel in my browser: ws://localhost:3000/?token=iYirTHOg-k0x
After this all goes directly over localhost:3001
Can someone explain how the auth system works for websockets? and how the flow of websockets work for .wasp in frontend and backend and let me know how I can plug in my external sources?
Should I define my own websocket system to externalize? or can I use the existing tooling with minimal changes?
