- Fix path to launch.sh - it's in the utils/ directory, not the top-level
- Version should be '1.2.0', previously it was some variable which looks like it comes from an external build program (this results in the snap being unable to build)
- Source of the novnc part has been fixed to reference the correct release file on github, not a 'build' directory on local machine (not present in the novnc sources)
- Websockify is now built direct from the 0.9.0 release on github. It appears that the version previously used (from the websockify package on Ubuntu) is too old to support 1.2.0 release of novnc (errors: "code 400, message Client must support 'binary' or 'base64' protocol")
- paths to launch.sh and svc_wrapper.sh have been corrected to where they actually are in the novnc sourc from github
Creating an Ubuntu Snap package to make noVNC easier to deploy.
Checks for the websockify binary in both the PATH (using which) and in the location where the Snap package places the binary. This is necessary for noVNC to be usable in a Snap. It doesn't affect the original functionality of git cloning websockify if it's not found in PATH or the Snap location.
Tim Edwards