Currently in the Fleet Manager app, the websocket client always tries to connect to http://localhost:8080/websocket/chat/, even on the production server which leads to a broken chat. This can be either by solved by just using the url /websocket/chat which then always connects to the websocket endpoint on the same domain or by distinguishing between production and development url.
Currently in the Fleet Manager app, the websocket client always tries to connect to
http://localhost:8080/websocket/chat/, even on the production server which leads to a broken chat. This can be either by solved by just using the url/websocket/chatwhich then always connects to the websocket endpoint on the same domain or by distinguishing between production and development url.See https://github.com/TU-CP18/cp18-backend/blob/a9c2e84a364efaa19e8fe19ad99cdf76cd7d8585/src/main/webapp/app/entities/chat/chat.service.ts#L47