The MANIFEST file

A Genero Archive MANIFEST file is a simple XML file providing the list of applications and services to make available. The MANIFEST file MUST be included in any Genero Archive file. You must create a MANIFEST file for each archive you create.

A MANIFEST file has a MANIFEST element at its root. Child elements can include the following,

Important: Element order. If child elements are present, they must be set in the order listed below or as shown in the sample.

One DESCRIPTION element. The DESCRIPTION element provides a textual description of the archive. It displays when listing archives.
0, or 1 TRIGGERS element. The TRIGGERS element (see TRIGGERS (for manifest)) specifies a trigger component which contains a program (e.g. fglrun ) or script to run to deploy or undeploy the application if the deployment framework is used.
0, or 1 RESOURCES element. The RESOURCES element specifies the directory in your archive file where images that are specific to your applications are found. The directory must be in the archive.
0, 1 or more APPLICATION elements. The APPLICATION element takes one mandatory attribute. The xcf attribute specifies the path to the application configuration file. The application configuration file must be in the archive. Include an APPLICATION element for each application in the archive.
0, 1 or more SERVICE elements. The SERVICE element takes one mandatory attribute. The xcf attribute specifies the path to the Web service configuration file. The Web service configuration file must be in the archive. Include a SERVICE element for each service in the archive.

Sample MANIFEST file:

<MANIFEST>
  <DESCRIPTION>my description</DESCRIPTION>
  <TRIGGERS component='comp_name'>
    <DEPLOY>deploy.sh</DEPLOY>
    <UNDEPLOY>undeploy.sh</UNDEPLOY>
  </TRIGGERS>
  <RESOURCES>res_dir</RESOURCES>
  <APPLICATION xcf='app.xcf' />
  <SERVICE xcf='app.xcf' />
</MANIFEST>