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 manage the application and the services related to it via a terminal.
Most server environments run on a headless configuration, but this is still subject 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.
The embedded Martini Runtime of Martini Desktop is inherently running in headless mode; it lacks the Martini Runtime Admin UI1. Meanwhile, the Martini Runtime Edition offers a headless and non-headless version of Martini.
Headless versus non-headless?
The headless distribution of the Runtime Edition removes access to the Martini Runtime Admin UI and its associated back-end components such as controllers. Meanwhile, the non-headless version retains the presence of the Martini Runtime Admin UI.
The Online and Runtime Editions include the CLI tool. The CLI tool gives users the capability to configure Martini using the command line interface.
The Desktop Edition of Martini is intended for non-production environments only, as a playground for users to explore the features of Martini and test their configurations.
While it is possible to configure Martini via IDE, support is partial and there are things you must still do via the Martini Runtime Admin UI or via the CLI tool like license management. After all, is a development environment for applications while the Martini Runtime Admin UI and CLI tool are for performing administrator functions. ↩