Currently the websockify wraps the VNC server. The advantage is that a separate process manager for the VNC server isn't needed. Only websockify needs to be managed by jupyter-server-proxy.
Since this uses unix sockets rebind.so shouldn't be necessary. I've tried patching websockify to wrap the process without introducing rebind.so but it didn't work. If this could be done websockify could be installed as a pure python package.
Currently the websockify wraps the VNC server. The advantage is that a separate process manager for the VNC server isn't needed. Only websockify needs to be managed by jupyter-server-proxy.
This wrapping behaviour is intended for use with
rebind.soto automatically map the VNC server's ports to some other value so that the original port can be websockified.Since this uses unix sockets rebind.so shouldn't be necessary. I've tried patching websockify to wrap the process without introducing
rebind.sobut it didn't work. If this could be done websockify could be installed as a pure python package.