Documentation:

Structure of the UBOS ManifestΒΆ

A Manifest JSON file has a type declaration, three required components, and two optional components:

{
  "type" : "<<type>>",
  "info" : {
     ... info section (not required but recommended)
  },
  "roles" : {
     ... roles section
  },
  "customizationpoints" : {
     ... customizationpoints section (optional)
  },
  "accessoryinfo" : {
     ... accessoryinfo section (for accessories only)
  }
}

The type declaration states whether the manifest is for an app or an accessory. An app uses:

"type" : "app"

while an accessory uses:

"type" : "accessory"

The optional info section contains user-friendly, localized information about the app or accessory. It is described in Info section.

The required roles section declares how the app wishes to be installed and configured with respect to Apache, MySQL, and other roles. It is described in Roles section.

Apps or accessories that support customization declare their parameters in an optional customizationpoints section. It is described in Customization points section.

In addition, accessories need to provide a accessoryinfo section to identify the app that they belong to. It is described in Accessoryinfo section.