Merge branch 'master' of git@github.com:kanaka/noVNC.wiki

Joel Martin
2011-03-21 16:34:45 -05:00

@@ -5,29 +5,31 @@
certificate using openssl. When asked for the common name, use the
hostname of the server where the proxy will be running:
openssl req -new -x509 -days 365 -nodes -out self.pem -keyout self.pem
```
openssl req -new -x509 -days 365 -nodes -out self.pem -keyout self.pem
```
* `tightvnc` provide a nice startup script that can be used to run
a separate X desktop that is served by VNC. To install and run the
server under Ubuntu you would do something like this:
`sudo apt-get install tightvncserver`
```
sudo apt-get install tightvncserver
vncserver :1
```
`vncserver :1`
The VNC server will run in the background. The port that it runs
on is the display number + 5900 (i.e. 5901 in the case above).
The VNC server will run in the background. The port that it runs
on is the display number + 5900 (i.e. 5901 in the case above).
* `x11vnc` can be used to share your current X desktop. Note that if
you run noVNC on the X desktop you are connecting to via VNC you
will get a neat hall of mirrors effect, but the the client and
server will fight over the mouse.
`sudo apt-get install x11vnc`
`x11vnc -forever -display :0`
```
sudo apt-get install x11vnc
x11vnc -forever -display :0
```
Without the `-forever` option, x11vnc will exit after the first
disconnect. The `-display` option indicates the exiting X display to
@@ -37,14 +39,15 @@
* To run the python proxy directly without using launch script (to
pass additional options for example):
`./utils/websockify source_port target_addr:target_port`
`./utils/websockify 8787 localhost:5901`
./utils/websockify source_port target_addr:target_port
./utils/websockify 8787 localhost:5901
* To activate the mini-webserver in websockify use the `--web DIR`
option:
`./utils/websockify --web ./ 8787 localhost:5901`
```
./utils/websockify --web ./ 8787 localhost:5901
```
* Point your web browser at http://localhost:8787/vnc.html. On the