Thomas Stollenwerk

Results 6 comments of Thomas Stollenwerk

In our case we are using a sandbox dev deployment with minikube and rabbitmq. Running on windows using miniport and NodePort you can easily setup the dev environment against `minikube.mshome.net:FIXED_PORT`....

In our case locking the NodePort was possible: ``` [...] service: type: NodePort override: service: spec: ports: - name: tcp-amqp protocol: TCP port: 5672 targetPort: 5672 nodePort: 35672 [...] ```...

Still work in progress. But I need to get rid of all the licensed prefabs before... ![grafik](https://user-images.githubusercontent.com/1308503/151677190-b417eeb4-8850-434b-b382-0a84696b83bc.png) ![grafik](https://user-images.githubusercontent.com/1308503/151677193-a44b0cfb-b26b-4c83-9fcf-fe31d43ddc3d.png) ![grafik](https://user-images.githubusercontent.com/1308503/151677209-99798417-537b-41e0-b22b-4b6eacacaa75.png) ![grafik](https://user-images.githubusercontent.com/1308503/151677226-d51dd1d8-99d3-401a-acbe-745409c37ccb.png) ![grafik](https://user-images.githubusercontent.com/1308503/151677287-c36f4341-e797-4934-84d3-ea5fc9a85e39.png)

F.e access to `KcpClient.socket.LocalEndpoint`

After patching this to get the client port I also found out, that there's no way to set custom socket options for the server side. I had to patch `CreateServerSocket`...