MobiusFlow has been containerised and is run via docker.
Below is an example docker-compose.yml file you could use when running MobiusFlow. In this example, an online version of MobiusFlow 1.19.1 is used. Note that, as well as the MobiusFlow service (labelled simply 'mobius'), the file also containers a reference to an nginx and mongodb containers.
The nginx container is used for port mapping, and mongodb container used as a database. Neither of these are required to run MobiusFlow.
This file can also be downloaded here:
It is important to include the correct licensing information within the environment variables of your docker-compose.yml file.
See the main article on licensing for a full explanation of what is required for online and offline licensing as well updating a given licence.
For MobiusFlow 1.x.x only
The service diagnostics and control page shows all of the configured services, their current status and controls to start and stop services.
The Run State column (2) shows the current run state of the services in a traffic light. The colours are defined as follows:
Grey - Not running, never started
Red - Not running, manually stopped
Amber - Starting or attempting to start
Green - Running
The Actions column (3) has start / stop buttons for each service. Services can be manually started or stopped by clicking on the action buttons.
These action buttons do not modify the value of the Run on Start checkbox on the services configuration page.
The service status column (4) shows the current status of all running services. In addition to a text message, the statuses are colour coded as follows:
Amber - starting or status unknown
Red - service is running but in fault (see text message for details)
Green - service is running and not in fault
The values shown in the Service Status column are tied to the service status object associated with the service. These status objects are automatically created and updated by the services as object profile ID 0001 with instance 0001. You can read the status of these objects but should not write to them.
The View Objects column (5) are hot-links to the Objects Diagnostics page, but filtered to only show objects belonging the the relevant service.
The Objects diagnostics page can be shown by clicking on the Objects button on the left of the screen (section 1 in image below) or by clicking on the View Objects hot-link described above. To view all objects belonging to all services use the Objects button (section 1 in image below).
Clicking on the plus sign (3) next to an object expands it to show all of its resources and their current values (2).
It is possible to manually modify a resource's value by writing to, or clearing a value in its priority array (see MobiusFlow Architecture). Click on a resource to display its full priority array. Click on a priority to modify its value or clear it.
Resource value modifications are temporary and could be overwritten by a service or Node-RED flow, and do not persist between service restarts or node reboots.
For MobiusFlow 1.x.x only
The configuration page is used to create and configure the MobiusFlow configuration for a Mobius node (see ). The page is split into five main sections:
The main menu
The services palette
The objects palette
The configuration tree
The service and object configuration section
The main menu is displayed on all pages. It allows switching between Configuration, Diagnostics, Node-RED Flows and Administration. The Administration option is only shown for users who have admin privileges.
The services palette shows the list of Mobius services that can be added to the configuration. To add a service to your configuration drag it from the services palette and drop it on to the configuration tree.
The objects palette shows the list of Mobius objects that can be added to the configuration. To add an object to your configuration drag it from the objects palette and drop it on to a service in the configuration tree.
The configuration tree shows the services and objects currently added to the configuration. Clicking on the triangles on the left of the tree either expands or contracts a branch of the tree. The currently selected item is shown as highlighted in orange.
To delete a service or object, hover over the item and click on the dustbin icon which appears to the right of the item.
Deleting a service deletes all associated objects
This section is dynamic and updates depending on which item has been selected in the configuration tree. If a service has been selected the service's configuration properties are displayed. Similarly, selecting an object or object resource shows the relevant configuration options.
Always click the Save Changes button to persist changes to a service, object or resource configuration. Any changes to a service, object or resource only become active after the service has been restarted on the diagnostics page.
The Administration page covers user management, backup and restore, licence settings, security as well as setting the node's Hub ID. The page is divided into corresponding tabs accordingly.
Users can be added, modified and deleted from within the User Management Tab on the Administration page.
Backup and restore functionality is accessed via the settings tab on the Administration page. A full article covering backup and restore can be found here.
All Mobius nodes are identified by their hub ID. This is a six character hexadecimal number and should be unique within any group of Mobius nodes. See MobiusFlow Architecture and MobiusFlow Uniform Resource Identifiers for more information about Hub IDs.