jcarr
/
noVNC
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Don't mention websockify like it's included 

We split it off to its own thing some time ago, so let's refer to
it that way.
This commit is contained in:
Pierre Ossman 2017-12-08 16:24:35 +01:00
parent 1bc11d7df5
commit 62bfc48759
1 changed files with 11 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
README.md
View File

@ -81,19 +81,21 @@ aware of:
### Server Requirements ### Server Requirements
Unless you are using a VNC server with support for WebSockets connections (such noVNC follows the standard VNC protocol, but unlike other VNC clients it does
as [x11vnc/libvncserver](http://libvncserver.sourceforge.net/), require WebSockets support. Many servers include support (e.g.
[QEMU](http://www.qemu.org/), or [x11vnc/libvncserver](http://libvncserver.sourceforge.net/),
[MobileVNC](http://www.smartlab.at/mobilevnc/)), you need to use a [QEMU](http://www.qemu.org/), and
WebSockets to TCP socket proxy. There is a python proxy included [MobileVNC](http://www.smartlab.at/mobilevnc/)), but for the others you need to
('websockify'). use a WebSockets to TCP socket proxy. noVNC has a sister project
[websockify](https://github.com/novnc/websockify) that provides a simple such
proxy.
### Quick Start ### Quick Start
* Use the launch script to start a mini-webserver and the WebSockets proxy * Use the launch script to automatically download and start websockify, which
(websockify). The `--vnc` option is used to specify the location of a running includes a mini-webserver and the WebSockets proxy. The `--vnc` option is
VNC server: used to specify the location of a running VNC server:
`./utils/launch.sh --vnc localhost:5901` `./utils/launch.sh --vnc localhost:5901`