| 2015-09-07 09:28:23 |
Simon Bazley |
description |
Summarising from https://answers.launchpad.net/ubuntu/+source/novnc/+question/271057
utils/launch.sh (present in the novnc source package) is a fairly essential part of this application. Without it a user really needs to know how to start up websockify manually, and all the documentation I found online, simply says start utils/launch.sh
Simply extracting the file, isn't enough, as it assumes a websockify is in the same (utils) folder, so applying this diff, makes it work perfectly with the existing novnc package.
30a31,32
> #WEBSOCKIFY=${HERE}/websockify
> WEBSOCKIFY=websockify
105c107
< ${HERE}/websockify --web ${WEB} ${CERT:+--cert ${CERT}} ${PORT} ${VNC_DEST} &
---
> ${WEBSOCKIFY} --web ${WEB} ${CERT:+--cert ${CERT}} ${PORT} ${VNC_DEST} & |
Summarising from https://answers.launchpad.net/ubuntu/+source/novnc/+question/271057
utils/launch.sh (present in the novnc source package) is a fairly essential part of this application. Without it a user really needs to know how to start up websockify manually, and all the documentation I found online, simply says start utils/launch.sh
Simply extracting the file, isn't enough, as it assumes a websockify executable is in the same folder as the script. Applying this diff, changes the call to make the call as long as websockify is on the path, this makes it work perfectly happily along with the existing websockify package (wherein the websockify executable is installed into /usr/bin).
30a31,32
> #WEBSOCKIFY=${HERE}/websockify
> WEBSOCKIFY=websockify
105c107
< ${HERE}/websockify --web ${WEB} ${CERT:+--cert ${CERT}} ${PORT} ${VNC_DEST} &
---
> ${WEBSOCKIFY} --web ${WEB} ${CERT:+--cert ${CERT}} ${PORT} ${VNC_DEST} & |
|
