Remote control (GUI)#

New in version 2.8.

See also

This section describes how to set up the GUI to connect to a server. To find information about setting up the actual server see Remote control (core).

DAF can run either locally or it can connect to a remote server that is running the DAF core. Users can choose between these two options by changing the connection client as shown in picture:

../../_images/gui-connection-select.png

Using LocalConnectionCLIENT will start DAF locally and anything the users do will be done locally. Using RemoteConnectionCLIENT will connect to a remote server and anything the users do including adding / removing accounts, retrieving logs, etc. will be done through a HTTP API which can also be HTTPS (recommended) if desired.

If the Edit button is clicked (in the top right corner) and RemoteConnectionCLIENT is selected, a new window will be opened, which allows customization of connection parameters.

../../_images/edit-remoteconnectionclient.png
class daf_gui.connector.RemoteConnectionCLIENT(host: str, port: int = 80, username: str | None = None, password: str | None = None, verify_ssl: bool | None = True)#

Client used for connecting to DAF running on a remote server though the HTTP protocol. The connection is based fully on request from the GUI (this client).

Parameters:
  • host (str) – The URL / IP of the host.

  • port (Optional[int]) – The HTTP port of the host. Defaults to 80.

  • username (Optional[str]) – The username to login with.

  • password (Optional[str].) – The password to login with.

  • verify_ssl (Optional[bool]) – Defaults to True. If True, connection will be refused when the certificate does not match the host name.

See also

When generating the DAF core script, remote access will also be configured if the RemoteConnectionCLIENT is selected.

Clicking on Edit when LocalConnectionCLIENT is selected will show an error.