Requirements

You can install the integrated TethysDash system via Docker or via direct installation of the underlying components.

Regardless of the method, the following explains what is required on your server to support TethysDash operations. The two installation methods are then described in later sections.

LRAUV vehicle configurations and mission files

As part of regular operations, TethysDash will access vehicle configurations and mission files from corresponding directories under version control using Git. These two directories will typically be clones of corresponding remote repositories.

In TethysDash, vehicle deployments are tied to Git tags, which allows to keep track of available missions and capabilities of each deployed vehicle.

There are configuration properties (depending on the installation method, see later sections) to indicate the location of these Git clones.

Remote private repositories?

If the referenced vehicle configurations and mission files are hosted on remote private repositories, you will need to provide the following as part of the TethysDash configuration:

  • The private SSH key to access those repositories;
  • The "known_hosts" file handled by ssh.

For details about the vehicle configuration and mission file repositories, please see the LRAUV documentation.

TODO

LRAUV team: please provide pointer to said documentation.

Email server

An email server with IMAP and SMTP capabilities is needed for managing emails to and from TethysDash. A dedicated email address is recommended since TethysDash will be managing the inbox and routing all incoming mail to designated folders (which it will create).

Tip

You may want to send incoming mail from Iridium and Argos to an email list or alias (such as tethys_incoming@my.server.com) so that additional users can configure the list/alias to temporarily "listen in" on emails.