pikers
/
piker
3
0
Fork 0
Code Issues 2 Pull Requests 5 Packages Projects Releases Wiki Activity
piker/dockering/ib/run_x11_vnc.sh

36 lines
875 B
Bash
Raw Normal View History

Drop password auth from vnc server Currently we're held back by an `asyncvnc` issue, https://github.com/barneygale/asyncvnc/issues/1 but even still, given we're running the container to be only accessible by localhost i'm not sure we need this for the moment (or at all) anyway.
2022-05-24 12:27:31 +00:00
#!/bin/sh
Spawn a live account gateway alongside paper This is like, super first-draft-y (and ideally we move to offering an `piker.data._ahab` super for this) but, it's a start at allowing easy setup of both paper and live `ib-gw` container spawning. We Expect the user to input creds for the live account manually and the vnc server is (hackily) only run inside the paper instance which most of the time seems to make it possible click on the live gui window and input creds manually. We also add extra files for the live instance: - a `dockering/ib/run_x11_vnc_live.sh` which is is a blank script that avoids running an `x11vnc` server in the line account cntr. - a `dockering/ib/jts_live.ini` config which manually sets the live gw to use the `4001` port for api connections. Further config tweaks: - IBC: drop the api dynamic port override, decrease login display timeout to the riskier but likely to be faster 20s. - `x11vnc` cmd: got back to using `rfbport` instead of `autoport`, drop `-logappend` so we see logging on docker console again, drop the frame cacheing flags and add in some x-hack disable flags.
2022-08-20 21:49:06 +00:00
# start vnc server and listen for connections
# on port specced in `$VNC_SERVER_PORT`
Drop password auth from vnc server Currently we're held back by an `asyncvnc` issue, https://github.com/barneygale/asyncvnc/issues/1 but even still, given we're running the container to be only accessible by localhost i'm not sure we need this for the moment (or at all) anyway.
2022-05-24 12:27:31 +00:00
x11vnc \
Only allow vnc client connections from localhost
2022-07-26 13:47:36 +00:00
-listen 127.0.0.1 \
-allow 127.0.0.1 \
Spawn a live account gateway alongside paper This is like, super first-draft-y (and ideally we move to offering an `piker.data._ahab` super for this) but, it's a start at allowing easy setup of both paper and live `ib-gw` container spawning. We Expect the user to input creds for the live account manually and the vnc server is (hackily) only run inside the paper instance which most of the time seems to make it possible click on the live gui window and input creds manually. We also add extra files for the live instance: - a `dockering/ib/run_x11_vnc_live.sh` which is is a blank script that avoids running an `x11vnc` server in the line account cntr. - a `dockering/ib/jts_live.ini` config which manually sets the live gw to use the `4001` port for api connections. Further config tweaks: - IBC: drop the api dynamic port override, decrease login display timeout to the riskier but likely to be faster 20s. - `x11vnc` cmd: got back to using `rfbport` instead of `autoport`, drop `-logappend` so we see logging on docker console again, drop the frame cacheing flags and add in some x-hack disable flags.
2022-08-20 21:49:06 +00:00
-rfbport "${VNC_SERVER_PORT}" \
Drop password auth from vnc server Currently we're held back by an `asyncvnc` issue, https://github.com/barneygale/asyncvnc/issues/1 but even still, given we're running the container to be only accessible by localhost i'm not sure we need this for the moment (or at all) anyway.
2022-05-24 12:27:31 +00:00
-display :1 \
-forever \
-shared \
Spawn a live account gateway alongside paper This is like, super first-draft-y (and ideally we move to offering an `piker.data._ahab` super for this) but, it's a start at allowing easy setup of both paper and live `ib-gw` container spawning. We Expect the user to input creds for the live account manually and the vnc server is (hackily) only run inside the paper instance which most of the time seems to make it possible click on the live gui window and input creds manually. We also add extra files for the live instance: - a `dockering/ib/run_x11_vnc_live.sh` which is is a blank script that avoids running an `x11vnc` server in the line account cntr. - a `dockering/ib/jts_live.ini` config which manually sets the live gw to use the `4001` port for api connections. Further config tweaks: - IBC: drop the api dynamic port override, decrease login display timeout to the riskier but likely to be faster 20s. - `x11vnc` cmd: got back to using `rfbport` instead of `autoport`, drop `-logappend` so we see logging on docker console again, drop the frame cacheing flags and add in some x-hack disable flags.
2022-08-20 21:49:06 +00:00
-bg \
-nowf \
-noxdamage \
-noxfixes \
Only allow vnc client connections from localhost
2022-07-26 13:47:36 +00:00
Spawn a live account gateway alongside paper This is like, super first-draft-y (and ideally we move to offering an `piker.data._ahab` super for this) but, it's a start at allowing easy setup of both paper and live `ib-gw` container spawning. We Expect the user to input creds for the live account manually and the vnc server is (hackily) only run inside the paper instance which most of the time seems to make it possible click on the live gui window and input creds manually. We also add extra files for the live instance: - a `dockering/ib/run_x11_vnc_live.sh` which is is a blank script that avoids running an `x11vnc` server in the line account cntr. - a `dockering/ib/jts_live.ini` config which manually sets the live gw to use the `4001` port for api connections. Further config tweaks: - IBC: drop the api dynamic port override, decrease login display timeout to the riskier but likely to be faster 20s. - `x11vnc` cmd: got back to using `rfbport` instead of `autoport`, drop `-logappend` so we see logging on docker console again, drop the frame cacheing flags and add in some x-hack disable flags.
2022-08-20 21:49:06 +00:00
# -nowcr \
# TODO: can't use this because of ``asyncvnc`` issue:
Drop password auth from vnc server Currently we're held back by an `asyncvnc` issue, https://github.com/barneygale/asyncvnc/issues/1 but even still, given we're running the container to be only accessible by localhost i'm not sure we need this for the moment (or at all) anyway.
2022-05-24 12:27:31 +00:00
# https://github.com/barneygale/asyncvnc/issues/1
Switch vnc server to port 3003
2022-06-03 14:17:50 +00:00
# -passwd 'ibcansmbz'
Spawn a live account gateway alongside paper This is like, super first-draft-y (and ideally we move to offering an `piker.data._ahab` super for this) but, it's a start at allowing easy setup of both paper and live `ib-gw` container spawning. We Expect the user to input creds for the live account manually and the vnc server is (hackily) only run inside the paper instance which most of the time seems to make it possible click on the live gui window and input creds manually. We also add extra files for the live instance: - a `dockering/ib/run_x11_vnc_live.sh` which is is a blank script that avoids running an `x11vnc` server in the line account cntr. - a `dockering/ib/jts_live.ini` config which manually sets the live gw to use the `4001` port for api connections. Further config tweaks: - IBC: drop the api dynamic port override, decrease login display timeout to the riskier but likely to be faster 20s. - `x11vnc` cmd: got back to using `rfbport` instead of `autoport`, drop `-logappend` so we see logging on docker console again, drop the frame cacheing flags and add in some x-hack disable flags.
2022-08-20 21:49:06 +00:00
# XXX: optional graphics caching flags that seem to rekt the overlay
# of the 2 gw windows? When running a single gateway
# this seems to maybe optimize some memory usage?
# -ncache_cr \
# -ncache \
# -no6 \
# -noipv6 \
# NOTE: this will prevent logs from going to the console.
# -logappend /var/log/x11vnc.log \
# where to start allocating ports
# -autoport "${VNC_SERVER_PORT}" \