You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 27, 2020. It is now read-only.
Let's add a configuration option to the native engine.. Such that it can be configured to connect to a VNC server on localhost and use this to expose display.
This way when installing tc-worker with native engine you just need to install a VNC server on localhost and set the engine configuration to use it, and enable the interactive plugin, then you have interactive display.
The implementation is rather easy... just returns a list of zero or one display, the VNC testing code already contains logic to extract screen resolution which could be reused, or this feature could be omitted since it's not critical. Then the actual thing is returning a pipe from OpenDisplay and copy from the pipe to a connection to the vnc server on localhost.
Note: this requires installing a vnc server on localhost, but it's a nice way to do it, as such vnc servers are readily available on most platforms. There might be some things to consider with respect to the per-task user feature...
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Let's add a configuration option to the native engine.. Such that it can be configured to connect to a VNC server on localhost and use this to expose display.
This way when installing tc-worker with native engine you just need to install a VNC server on localhost and set the engine configuration to use it, and enable the interactive plugin, then you have interactive display.
The implementation is rather easy... just returns a list of zero or one display, the VNC testing code already contains logic to extract screen resolution which could be reused, or this feature could be omitted since it's not critical. Then the actual thing is returning a pipe from
OpenDisplay
and copy from the pipe to a connection to the vnc server on localhost.Note: this requires installing a vnc server on localhost, but it's a nice way to do it, as such vnc servers are readily available on most platforms. There might be some things to consider with respect to the per-task user feature...
The text was updated successfully, but these errors were encountered: