A headless environment is an environment that does not include support for a graphical user interface (GUI). An application deployed in this type of environment is typically managed via a command line interface (CLI) where administrators execute a variety of commands to manipulate the application and the services related to it via a terminal.
Most server environments run on a headless configuration, but this is still subjective to the user’s preference. Headless systems are known for having an upper hand security-wise compared to traditional systems with GUIs and they are also known to work more efficiently because they have no display to process, thus being faster.
TORO Integrate instances running on a Desktop subscription are inherently running in headless environments as they lack the Server Admin UI and the primary means of configuring them are via the CLI tool1. The Server Edition offers a headless and non-headless version of TORO Integrate.
Headless versus non-headless?
The headless distribution of the Server Edition merely removes access to the Server Admin UI and its associated back-end components such as controllers. Meanwhile, the non-headless version retains the presence of the Server Admin UI.
The Desktop Edition of TORO Integrate is intended for non-production environments only, as a playground for users to explore the features of TORO Integrate and test their configurations.
While it is possible to configure TORO Integrate via Coder, support is partial and there are things you must still do via the Server Admin UI or via the CLI tool like license management. After all, Coder is a development environment for integrations while the Server Admin UI and CLI tool are for performing administrator functions. ↩